One Hat Cyber Team
Your IP :
172.71.120.55
Server IP :
188.114.97.7
Server :
Linux advantage-project 5.14.0-503.26.1.el9_5.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Feb 19 16:28:19 UTC 2025 x86_64
Server Software :
Apache/2.4.62 (Rocky Linux) OpenSSL/3.2.2
PHP Version :
8.3.17
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
proc
/
self
/
root
/
usr
/
share
/
mysql
/
dutch
/
Edit File:
errmsg.sys
�� N� � K � � � 4 � � > z � � G � � m � � ^ � � � / b � � � - J � � $ 9 + U i � 0 S p � � � � Y v � + H k � � � � H t � Q � � ' y � � � O i � # � . t � ( � � [ s � � � ' � � � & J , h � � � Q z � � � � ) w � B j � � � � � , � � � � 0 S � p � 5! j! �! �! -" T" �" �" # 3# Z# q# �# �# �# +$ \$ �$ �$ % C% �% �% �% >& & �& M' p' �' �' O( �( �( �( ) =) h) �) �) * B* e* �* �* �* + ?+ �+ �+ , �, �, Z- �- . a. �. / \/ �/ �/ �/ :0 �0 �0 �0 #1 x1 �1 2 /2 s2 �2 �2 3 F3 c3 �3 �3 ?4 h4 �4 5 c5 �5 �5 !6 N6 �6 �6 �6 47 x7 �7 �7 8 ,8 P8 �8 �8 �8 9 69 v9 �9 �9 o: �: �: ; ; �; �; 2< O< p< �< �< &= T= ~= �= �= > X> �> �> ? <? �? s@ �@ A �A B /B PB �B �B �B KC gC �C �C =D �D �D �D jE �E �E �E %F NF �F �F �F G JG _G tG �G �G �G �G �G H PH uH �H �H vI �I �I �I J +J MJ nJ �J �J �J �J �J K 5K LK dK yK �K �K �K "L OL qL �L �L �L 7M yM �M �M N 6N kN �N �N �N sO �O P �P �P �P Q 'Q VQ �Q �Q �Q �Q "R RR �R �R �R S KS pS �S �S �S �S T ;T fT �T �T �T U BU mU �U �U �U V BV \V �V �V W =W TW �W �W !X ~X �X Y =Y pY �Y �Y �Y -Z ]Z �Z �Z �Z Z[ �[ �[ �\ N] �] [^ �^ �^ _ T_ �_ �_ #` t` �` a ba �a b Nb fb �b c 5c qc �c �c Id �d ?e e �e !f qf �f �f >g �g �g )h nh �h Ei fi �i �i 9j ej �j �j �j &k ^k hk rk �k �k :l _l {l �l 3m �m �m 5n |n �n �n (o ko �o p Cp �p �p q Bq wq �q �q /r ar �r �r *s �s �s �s Tt �t �t u +u `u �u �u `v �v �v �v 'w _w �w �w �w ox �x �x &y Ey gy �y �y �y �y z gz �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 � * � � 7 t � � � � 2 � � � � � � q � � � � � g � � * W � � 6 � � : � � a � � " c � � � � � . e � � � � 3 c � G � � � 4 l � � 8 S � � % � s � � / � ! �! :" �" �" Y# k# �# �# �# $ ,$ I$ % U% �% �% O& �& �& �& �& ,' V' �' �' �' �' �' ( 7( [( () �) �) E* z* /+ �+ �+ <, �, 4- �- -. �. �. 8/ Y/ �/ �/ �/ 0 :0 k0 �0 �0 �0 1 �1 �1 �1 -2 �2 �2 Z3 �3 4 44 T4 ~4 �4 �4 +5 _5 �5 �5 �5 "6 q6 �6 �6 H7 �7 �7 A8 w8 �8 69 �9 �9 : D: v: �: �: ; G; x; �; �; �; �; �; =< �< �< $= ~= �= �= -> �> �> �> ]? �? @ ]@ �@ SA B �B �B �B 3C qC �C D ?D uD �D 8E �E F 6F TF �F �F ZG �G �G 6H xH �H I ]I �I �I �I qJ �J �J %K YK �K �K L WL L �L M LM �M �M N ;N `N �N �N EO �O �O �P �P Q 8Q lQ �Q �Q GR �R �R ?S �S �S ;T �T dU V �V W X ;X jX �X �X �X �X 4Y UY pY �Y �Y �Y �Y $Z ]Z �Z �Z �Z 7[ _[ �[ �[ $\ q\ �\ �\ �] �] ^ @^ �^ �^ )_ �_ ` �` �` a Ha za �a �a Fb tb �b �b c Rc �c �c d Dd �d 9e ne |e �e f ff �f �f �f $g tg �g �g h �h �h �h 7i �i �j �j 2k k �k �l 6m �m �m n \n �n Mo �o �o zp )q fq �q �q Sr �r �r s os t �t �u ev �v x Lx �x �x y �y �y Az �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 � J c � � � � � � � � M \ n � � < � � ! k � ] � � ' i � � � T | � � � * M | ( � � � = k � � � C p t � � � \ � � � � � m � � � ! q! �! �! �! " P" r" �" # `# �# �# x$ % �% �% & Z& �& !' Y' �' 4( �( %) J) v) �) �) �) * <* x* + ^+ �+ ], �, %- �- �- . L. �. �. �. b/ �/ �/ �/ `0 �0 �0 1 :1 X1 �1 �1 �1 �1 �1 \2 �2 %3 03 ;3 H3 U3 `3 �3 �3 &4 44 U4 g4 �4 �4 �4 /5 d5 �5 �5 6 <6 �6 �6 �6 7 .7 �7 �7 8 48 f8 �8 �8 =: �: .; Y; �; {< = �= �= �= > &> Y> �> �> �> %? H? H@ �@ �@ A <A nA �A �A B hB �B �B �B �C �D �D �D .E �E �E F 4F `F �F �F IG sG �G �G FH �H �H �H I AI fI �I �I J :J WJ �J K K @K mK �K �K L <L JL XL hL �L M :N VN �N �N �O �P �P �P "Q <Q ~Q �Q �Q R 5R eR �R �R �R S 5S dS wS �S �S �S T XT �T �T U 8U WU rU �U �U �U V BV oV �V �V W )W RW uW �W �W X 7X jX �X �X �X Y 8Y |Y �Y $Z VZ �Z �Z �Z [ 8[ W[ ~[ �[ �[ �[ \ A\ �\ �\ ,] |] �] 4^ z^ �^ �^ q_ �_ q` �` /a �a #b [b �b �d e Ue f jf �f �f g Dg �g �g h eh �h �h 7i [i �i |j #k Jk kk �k !l �l �l m m hm m �m �m �m Ln jn �n �n (o uo �o �o p Cp �p ,q �q �q Or �r �r �r %s Ks �s �s t _t �t �t �u �u v Zv �v �v $w fw �w �w x Dx .y �y �z �{ �{ �{ *| I| b| y| �| �| �| )} n} �} ~ N~ �~ @ � � >� f� �� Ё �� 3� j� �� � �� � � �� �� ?� v� �� � ^� �� چ � G� �� � K� }� �� � 8� � щ � \� �� � � � � �� �� � �� C� y� ҍ &� E� �� �� X� ~� �� � � B� l� �� �� � _� �� ˑ � g� �� � � n� � �� %� O� �� Е �� "� 5� X� �� �� � %� M� �� �� З � Q� �� Ҙ �� &� l� �� ę �� � C� �� Κ 3� K� p� �� �� ؛ $� ?� �� ]� {� �� Н � k� �� �� O� �� � � A� �� � �� � U� R� �� �� ڤ �� F� �� �� "� R� Ч N� Ш �� 4� ;� u� ث � h� �� ά �� � �� � A� �� �� Y� o� ѯ � � L� �� �� � �� m� �� �� x� � c� ʴ � �� � x� �� �� �� � "� ɸ �� 2� d� �� � � h� �� ѻ �� `� �� Ҽ � � :� b� �� Ž � "� M� |� �� �� c� �� �� �� B� �� � 7� �� � � K� {� �� �� +� �� �� �� � z� �� S� �� �� � L� �� �� �� � @� �� �� 5� �� � t� �� � � � � R� p� �� �� �� "� G� �� �� h� �� � N� �� �� �� H� j� �� �� � a� �� �� �� !� �� r� �� �� �� � 8� l� �� �� � i� �� �� �� � $� G� g� �� �� �� .� Y� �� �� �� I� �� � o� �� �� �� � ;� �� �� � 8� a� �� �� � ,� Y� �� � ,� e� �� �� �� �� � B� x� �� �� �� &� ]� t� �� �� �� � 9� l� �� �� �� '� I� r� �� �� '� k� �� �� $� o� �� �� �� �� w� �� �� �� >� �� �� � �� � .� d� �� �� �� �� � ;� N� �� � <� i� �� � >� �� �� 0� }� �� �� F� �� � �� � 8� �� �� +� a� �� S� �� � x� �� � H� c� �� �� .� [� �� �� �� B� {� �� �� ,� � �� � M� �� �� 9� s� �� � � ,� x� � !� �� �� L� n� 9� �� �� �� � �� !� G� �� �� =� �� � � �� � � W� p� �� � N� �� U � ) 0 � ! c � � W w � � � Y � _ � / ] � � � � � # � $ � 6 � � ; � F o � � R � � � � � A � G � � � ? o � � � 0 [ _ � � / j n � � 9 � . � � [ � � I m � � L � � - _ � � " r � � ( | � { � � / c � � � ! M! �! �! &" ~" �" # *# O# s# �# $ O$ o$ �$ �$ �$ % a% �% �% & 6& <& �& �& �' �' x( �( `) ) �) �) * �* + d+ �+ , :, �, �, �, S- k- �- M. �. / 0 l0 �0 �0 �0 �0 �0 �0 �0 �0 �0 1 T1 W1 j1 �1 2 K2 N2 x2 �2 �2 �2 3 !3 �3 4 V4 �4 5 G5 a5 5 �5 6 C6 l6 �6 �6 ?7 �7 �7 %8 N8 �8 �8 T9 �9 �: 8; u; �; �; �< = 3= e= �= �= �= �= +> F> �> �> �> ? *? T? |? �? �? �? �? @ @ #@ W@ �@ �@ �@ A -A \A �A �A �A B (B UB �B �B �B C :C \C �C �C �C �C VD �D �D �D PE ~E �E �E 7F hF �F �F �F G QG oG �G �G H =H hH �H �H I (I dI �I �I J .J WJ �J �J K 9K _K �K �K �K L =L WL oL �L �L 2M �M bN �N �N O SO �O �O �O P QP P �P �P Q MQ �Q �Q �Q R GR bR �R �R �R �R S @S oS �S �S �S T IT mT �T �T �T �T U U 6U aU �U �U 0V 3V �V W PW �W �W �W �W �W �W �W /X �X �X Y EY �Y �Z @[ }[ *\ �\ �] *^ q^ �^ �^ �^ D_ e_ t_ �_ �_ �_ /` a` �` �` �` a Qa �a �a �a b (b Wb �b �b %c �c �c �c �c d "d %d Gd }d �d �d e ;e ce �e �e f Tf �f �f �f g Fg �g �g �g �g &h Ih mh �h �h *i Vi |i �i �i �i �i j ;j ej j �j �j �j 8k yk �k �k �k l @l ll �l �l 7m Hm rm �m �n Co �o �o �o p 0p bp �p �p Sq �q �q �q >r Ar �r �r �r �r 0s �s �t u (u Ru �u �u v >v lv �v �v �v �v &w Bw [w ww �w �w x 8x Rx vx �x �x �x Gy yy �y z nz �z t{ �{ �{ �| (} �} ~ �~ �~ _ � � *� U� O� Ձ _� �� �� � 1� [� �� �� � F� � �� � I� �� �� � +� y� �� ҆ ;� �� Ӈ D� �� !� �� ߉ 1� �� ڊ � o� Ջ 1� �� � }� �� l� � � �� � Z� �� B� c� �� +� �� ђ �� !� [� �� œ � ;� |� �� �� #� a� �� � j� �� ʖ ڗ D� � o� �� ך � ]� �� � [� �� Ϝ � 5� �� �� � �� J� �� � �� � V� �� � Z� �� U� ѣ w� � B� �� � W� �� ǧ �� N� ܨ \� � l� ̪ #� �� ܫ � ;� _� �� � x� ҭ (� m� ٮ H� o� ܯ M� �� �� n� �� }� ̲ � � &� F� |� �� ̳ � �� �� =� �� ε �� M� �� �� � �� � <� �� P� ̺ /� � �� � � O� �� � U� �� � v� � � Q� �� � h� � Z� �� �� 5� �� �� � h� �� �� ]� �� � �� �� E� �� �� )� {� �� "� �� �� �� � \� �� �� b� �� �� �� Q� � �� �� � D� �� 7� _� �� � �� �� � >� r� �� �� � F� |� �� �� 9� k� �� !� \� �� �� ;� �� �� �� � H� �� .� c� �� K� �� �� � S� �� �� f� � p� �� ;� y� �� � a� �� � =� �� �� R� �� �� <� �� H� � �� E� �� �� � M� n� �� �� .� [� �� � �� �� �� �� � b� �� �� � H� �� � � h� �� � � �� �� -� ]� �� �� �� � $� >� [� �� �� �� �� � <� �� �� �� � 4� �� �� �� �� 4� l� �� �� � ?� �� � ;� U� �� � � N� �� �� � #� T� a� �� � � A� d� �� �� � M� {� ~� �� � � (� b� �� �� � � �� � � z� � 4� l� �� � � N z � � < $ t w z } � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � ! $ ' * - 0 3 6 9 < ? B E H K N Q T W Z ] ` c f i l o r u x { ~ � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � T W Z ] ` c f i l o r u x { ~ � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � # & ) , / 2 5 8 ; > A D G J M P S V Y \ _ b � � [ � � � � � � � � . Q y � * - � � ` � T � � , k � � : l � � , / 2 5 8 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 } � � � � � � � � � � � � � � � � � � � � � � � " % ( + . 1 4 7 : = @ C F I L O R U X [ ^ a d g j m p s v y | � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � d g j � � � � � � ! $ ' * - 0 3 6 � � i � ) c � � > � � � 2 } � � � � ? ~ � G t � � H ~ � N! �! �! �" �" x# 6$ 9$ <$ �$ �$ ;% i% l% o% �% �% �% �% �% �% �% E& �& �& K' u' �' ( E( |( �( �( �( 9) �) �) �) <* + �+ �+ a, �, �, �, �, - - - - - - - - - - - !- $- '- *- -- 0- 3- 6- 9- <- ?- B- E- H- K- N- Q- T- W- Z- ]- `- c- f- i- l- o- r- u- x- {- ~- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- �- . . . . . . . . . . . #. &. ). ,. K. N. Q. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �. / / / / / / / / / / / !/ $/ '/ */ -/ 0/ 3/ 6/ 9/ </ ?/ B/ E/ H/ K/ N/ Q/ T/ W/ Z/ ]/ `/ c/ f/ i/ l/ o/ r/ u/ x/ {/ ~/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ �/ 0 0 0 0 0 0 0 0 0 0 0 #0 &0 )0 ,0 /0 20 50 80 ;0 >0 A0 D0 G0 J0 M0 P0 S0 V0 Y0 \0 _0 b0 e0 h0 k0 n0 q0 t0 w0 z0 }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 1 1 1 1 �1 �1 !2 �2 �2 3 @3 �3 �3 �3 ,4 \4 �4 �4 �4 �4 5 L5 �5 �5 6 ,6 Q6 r6 �6 �6 �6 7 C7 n7 �7 �7 8 ;8 �8 �8 �8 �8 9 B9 �9 : ,: h: �: �: ); m; �; I< �< �< �< �< = <= �= �= <> k> �> �> �> u? �? �? �? �? @ @ @ @ @ @ @ @ �@ �@ �@ �A �A �A �A �A OB zB �B C �D NE kE �E F �F �G HH cH �H �H �H �H I @J �J �K �K L ?L �L �L �L �L �L �L �L �L �L �L �L �L ,M VM YM wM zM �M �M �M �M N N N N N N N N N #N &N )N ,N /N 2N bN eN hN kN nN qN tN wN zN }N �N �N �N �N �N �N �N �N �N �N �N O O 8O [O ^O &P )P ,P /P 2P 5P 8P ;P >P AP DP GP JP MP PP SP VP YP �P �P �Q R R R R R WR �R �R �R S S 3S xS �S �S T �T �T �T �T �T �T �T �T �T �T �T �T EU HU TV WV ZV �V 'W �W �X �X Z �Z [ �[ @\ U\ }\ �] ^ �^ �^ �^ $_ �_ 2` }` �` �` �` �` a 4a Pa �a �a b Jb Xb yb c �c �c �c ,d Kd td �d �d e Be je �e Nf �f �f �f Qg �g �g [h �h �h �h �h i @i ]i �i �i �i j �j k �k �k �k �k "l Pl �l �l (m lm �m �m On �n �n No so �o �o �o �o p bp �p �p �p �p q q [q �q �q �q �q �q �q �q �q �q #r ^r �r �r 0s �s $t �t u -u gu �u �u �u qv �v w �w x kx �x y Xy �y �y 8z �z o{ �{ �{ | >| �| �| 2} Z} {} �} ,~ d~ � � �� ?� �� ,� a� Ԃ � � S� �� �� � G� J� �� � #� B� d� � �� j� �� �� ̆ � � $� `� �� ̇ � \� ͈ � )� �� �� �� 1� j� �� � e� ˋ � D� �� �� m� �� � v� � � U� �� ԏ @� �� *� �� �� w� � H� �� � '� w� ה � D� �� � � �� � 6� �� �� � 6� �� �� � 3� k� Ǚ � Q� {� �� ך � J� v� � � #� 8� x� Ȝ � V� w� �� � �� � 7� _� �� Ş � ^� � � m� � 4� �� � �� � �� -� ^� �� � �� � U� �� ʧ � � !� �� �� Ũ � � �� � � >� ~� �� � =� �� �� $� ?� �� e� �� � � 9� v� �� ծ !� f� �� �� � y� Ӱ (� m� Ʊ � Q� �� *� �� M� � �� ִ +� x� õ �� (� M� l� �� �� � ^� �� � L� �� Ӹ � L� �� � �� � K� b� �� ƻ � ܼ � � � K� �� � _� �� �� � S� � � �� � �� �� �� g� �� � � -� r� �� �� �� �� 5� X� �� @� �� �� �� �� �� o� 4� k� � #� r� �� D� �� '� �� �� d� �� `� �� � e� �� � b� �� �� :� X� �� � �� <� r� %� (� k� �� �� � � 6� r� �� a� �� �� �� �� �� �� � !� $� '� *� -� 0� 3� 6� 9� <� ?� B� E� H� K� N� Q� T� �� �� �� M� P� S� V� Y� \� �� �� � F� h� k� �� �� �� � Y� �� �� T� W� .� �� �� �� l� � �� � �� �� *� �� �� q� :� �� �� N� �� � I� �� �� E� �� �� 9� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� � � � � � � � � � � � !� $� '� *� g� �� �� ,� k� �� �� �� M� �� � �� �� 3� 6� �� (� �� \� z� �� �� J� |� �� �� �� � �� l� &� � �� � � � �� %� m� � � u� �� �� �� �� ' � ] � � < j � � � � 5 ~ � + W � E � � A � H w � & k � � v � $ � � � � k � � � � � M u � # � � � y 6 n � � � � " H K � � � P! �! _" �" y# �# $ )$ _$ �$ �$ �% �& �' �( �) * �* W+ , l, �, - #- 7- Q- �- �- =. p. �. �. �. &/ 5/ V/ 0 c1 �1 �1 �1 2 T2 w2 �2 3 a3 �3 4 4 �4 35 7 B7 V9 : z: �: ; �; �; �< |= �= -> n> �> \? �? �? �@ @A �A �A �A B 9B �B �B �B �B �B �C �C /D 2D 5D E �E HF vF �F G >G �G �G $H �H I QI �I &J uJ �J rK (L �L �M iN >O �O �O P PP �P �P �P !Q EQ jQ �Q �Q �Q -R �R OS �S �S T eT �T �T �T U >U �U �U �V RW X �Z :] c] �] �] �] [^ �^ _ h_ �_ �_ <` �` �a b �b dc �c ?d �d �d e $e Me f f bf �f �f $g sg �g �g �g h Lh �h �h �h �h i i )i Gi Zi �i `j �j k fk �k �l 8n }n bp tp �p �p �p q 'q Wq �q 0r �r $s }s �s 0t {t �t 'u {u �u �u Nv �v �v �w �w y sy �y �y Xz �z �z S{ �{ V| �| G} �} "~ g~ � � ~� � !� �� � #� ]� ҂ � 8� a� �� �� � .� Z� �� �� E� �� � {� ۆ =� �� � L� j� �� �� �� � � � &� I� w� �� �� �� � C� �� �� � �� � <� ɍ P� � b� �� �� � � A� � �� � � B� �� � {� �� ޔ hashchk isamchk NEE JA Kan 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 reeds Kan database '%-.192s' niet verwijderen; database bestaat niet Fout 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 tabel Kan 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 veranderingen Sorteren afgebroken View '%-.192s' bestaat niet voor '%-.192s' Fout %d - '%-.192s' van tabel handler Tabel handler voor '%-.192s' heeft deze optie niet Kan record niet vinden in '%-.192s' Verkeerde info in file: '%-.200s' Verkeerde zoeksleutel file voor tabel: '%-.200s'; probeer het te repareren Oude zoeksleutel file voor tabel '%-.192s'; repareer het! '%-.192s' is alleen leesbaar Geen geheugen meer. Herstart server en probeer opnieuw (%d bytes nodig) Geen geheugen om te sorteren. Verhoog de server sort buffer size Onverwachte eof gevonden tijdens het lezen van file '%-.192s' (Errcode: %d - %s) Te veel verbindingen 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 Kan de hostname niet krijgen van uw adres Verkeerde handshake Toegang geweigerd voor gebruiker: '%-.48s'@'%-.64s' naar database '%-.192s' Toegang geweigerd voor gebruiker: '%-.48s'@'%-.64s' (Wachtwoord gebruikt: %s) Geen database geselecteerd Onbekend commando Kolom '%-.192s' kan niet null zijn Onbekende database '%-.192s' Tabel '%-.192s' bestaat al Onbekende tabel '%-.129s' Kolom: '%-.192s' in %-.192s is niet eenduidig Bezig met het stoppen van de server Onbekende kolom '%-.192s' in %-.192s Opdracht gebruikt '%-.192s' dat niet in de GROUP BY voorkomt Kan '%-.192s' niet groeperen Opdracht heeft totaliseer functies en kolommen in dezelfde opdracht Het aantal kolommen komt niet overeen met het aantal opgegeven waardes Naam voor herkenning '%-.100s' is te lang Dubbele kolom naam '%-.192s' Dubbele zoeksleutel naam '%-.192s' Dubbele ingang '%-.192s' voor zoeksleutel %d Verkeerde kolom specificatie voor kolom '%-.192s' %s bij '%-.80s' in regel %d Query was leeg Niet unieke waarde tabel/alias: '%-.192s' Foutieve standaard waarde voor '%-.192s' Meerdere primaire zoeksleutels gedefinieerd Teveel zoeksleutels gedefinieerd. Maximaal zijn %d zoeksleutels toegestaan Teveel zoeksleutel onderdelen gespecificeerd. Maximaal %d onderdelen toegestaan Gespecificeerde zoeksleutel was te lang. De maximale lengte is %d Zoeksleutel kolom '%-.192s' bestaat niet in tabel BLOB kolom '%-.192s' kan niet gebruikt worden bij zoeksleutel specificatie Te grote kolomlengte voor '%-.192s' (max = %lu). Maak hiervoor gebruik van het type BLOB Er 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 openen Tabel '%-.192s' heeft geen INDEX zoals deze gemaakt worden met CREATE INDEX. Maak de tabel opnieuw De argumenten om velden te scheiden zijn anders dan verwacht. Raadpleeg de handleiding Bij 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 reeds Records: %ld Verwijderd: %ld Overgeslagen: %ld Waarschuwingen: %ld Records: %ld Dubbel: %ld 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 Het 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: %ld You can't specify target table '%-.192s' for update in FROM clause Onbekend thread id: %lu U bent geen bezitter van thread %lu Geen tabellen gebruikt. Teveel strings voor kolom %-.192s en SET Het 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 TABLES Blob veld '%-.192s' can geen standaardwaarde bevatten Databasenaam '%-.100s' is niet getoegestaan Niet 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 Fout Onbekende procedure %-.192s Foutief aantal parameters doorgegeven aan procedure %-.192s Foutieve parameters voor procedure %-.192s Onbekende tabel '%-.192s' in %-.32s Veld '%-.192s' is dubbel gespecificeerd Ongeldig gebruik van GROUP-functie Tabel '%-.192s' gebruikt een extensie, die niet in deze MySQL-versie voorkomt. Een tabel moet minstens 1 kolom bevatten De tabel '%-.192s' is vol Onbekende character set: '%-.64s' Teveel tabellen. MySQL kan slechts %d tabellen in een join bevatten Te veel velden Rij-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-conditions Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler Kan functie '%-.192s' niet laden Kan functie '%-.192s' niet initialiseren; %-.192s Geen pad toegestaan voor shared library Functie '%-.192s' bestaat reeds Kan shared library '%-.192s' niet openen (Errcode: %d %-.128s) Kan functie '%-.128s' niet in library vinden Functie '%-.192s' is niet gedefinieerd Host '%-.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 server U gebruikt MySQL als anonieme gebruiker en deze mogen geen wachtwoorden wijzigen U moet tabel update priveleges hebben in de mysql database om wachtwoorden voor anderen te mogen wijzigen Kan geen enkele passende rij vinden in de gebruikers tabel Passende rijen: %ld Gewijzigd: %ld Waarschuwingen: %ld 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 Kolom aantal komt niet overeen met waarde aantal in rij %ld Kan tabel niet opnieuw openen: '%-.192s Foutief gebruik van de NULL waarde Fout '%-.64s' ontvangen van regexp Het mixen van GROUP kolommen (MIN(),MAX(),COUNT()...) met no-GROUP kolommen is foutief indien er geen GROUP BY clausule is Deze 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 lang Tabel '%-.192s.%-.192s' bestaat niet Deze toegang (GRANT) is niet toegekend voor gebruiker '%-.48s' op host '%-.255s' op tabel '%-.192s' Het used commando is niet toegestaan in deze MySQL versie Er is iets fout in de gebruikte syntax Delayed insert thread couldn't get requested lock for table %-.192s Too many delayed threads in use Afgebroken verbinding %ld naar db: '%-.192s' gebruiker: '%-.48s' (%-.64s) Groter pakket ontvangen dan 'max_allowed_packet' Kreeg leesfout van de verbindings pipe Kreeg fout van fcntl() Pakketten in verkeerde volgorde ontvangen Communicatiepakket kon niet worden gedecomprimeerd Fout bij het lezen van communicatiepakketten Timeout bij het lezen van communicatiepakketten Fout bij het schrijven van communicatiepakketten Timeout bij het schrijven van communicatiepakketten Resultaat string is langer dan 'max_allowed_packet' Het gebruikte tabel type ondersteunt geen BLOB/TEXT kolommen Het gebruikte tabel type ondersteunt geen AUTO_INCREMENT kolommen INSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLES Incorrecte kolom naam '%-.100s' De gebruikte tabel 'handler' kan kolom '%-.192s' niet indexeren Niet alle tabellen in de MERGE tabel hebben identieke gedefinities Kan niet opslaan naar table '%-.192s' vanwege 'unique' beperking BLOB kolom '%-.192s' gebruikt in zoeksleutel specificatie zonder zoeksleutel lengte Alle delen van een PRIMARY KEY moeten NOT NULL zijn; Indien u NULL in een zoeksleutel nodig heeft kunt u UNIQUE gebruiken Resultaat bevatte meer dan een rij Dit tabel type heeft een primaire zoeksleutel nodig Deze versie van MySQL is niet gecompileerd met RAID ondersteuning U gebruikt 'safe update mode' en u probeerde een tabel te updaten zonder een WHERE met een KEY kolom. %s Zoeksleutel '%-.192s' bestaat niet in tabel '%-.192s' Kan tabel niet openen De 'handler' voor de tabel ondersteund geen %s Het is u niet toegestaan dit commando uit te voeren binnen een transactie Kreeg fout %d - '%-.192s' tijdens COMMIT Kreeg fout %d - '%-.192s' tijdens ROLLBACK Kreeg fout %d tijdens FLUSH_LOGS Kreeg fout %d tijdens CHECKPOINT Afgebroken verbinding %u naar db: '%-.192s' gebruiker: '%-.48s' host: '%-.255s' (%-.64s) De 'handler' voor de tabel ondersteund geen binaire tabel dump Binlog closed, cannot RESET SOURCE Gefaald tijdens heropbouw index van gedumpte tabel '%-.192s' Fout van master: '%-.64s' Net fout tijdens lezen van master Net fout tijdens schrijven naar master Kan geen FULLTEXT index vinden passend bij de kolom lijst Kan het gegeven commando niet uitvoeren, want u heeft actieve gelockte tabellen of een actieve transactie Onbekende systeem variabele '%-.64s' Tabel '%-.192s' staat als gecrashed gemarkeerd en dient te worden gerepareerd Tabel '%-.192s' staat als gecrashed gemarkeerd en de laatste (automatische?) reparatie poging mislukte Waarschuwing: Roll back mislukt voor sommige buiten transacties gewijzigde tabellen Multi-statement transactie vereist meer dan 'max_binlog_cache_size' bytes opslag. Verhoog deze mysqld variabele en probeer opnieuw Deze operatie kan niet worden uitgevoerd met een actieve slave, doe eerst STOP SLAVE Deze operatie vereist een actieve slave, configureer slave en doe dan START SLAVE De server is niet geconfigureerd als slave, fix in configuratie bestand of met CHANGE MASTER TO Could not initialize connection metadata structure; more error messages can be found in the MySQL error log Kon slave thread niet aanmaken, controleer systeem resources Gebruiker %-.64s heeft reeds meer dan 'max_user_connections' actieve verbindingen U mag alleen constante expressies gebruiken bij SET Lock wacht tijd overschreden Het totale aantal locks overschrijdt de lock tabel grootte Update locks kunnen niet worden verkregen tijdens een READ UNCOMMITTED transactie DROP DATABASE niet toegestaan terwijl thread een globale 'read lock' bezit CREATE DATABASE niet toegestaan terwijl thread een globale 'read lock' bezit Foutieve parameters voor %s '%-.48s'@'%-.64s' mag geen nieuwe gebruikers creeren Incorrecte tabel definitie; alle MERGE tabellen moeten tot dezelfde database behoren Deadlock gevonden tijdens lock-aanvraag poging; Probeer herstart van de transactie Het gebruikte tabel type ondersteund geen FULLTEXT indexen Kan foreign key beperking niet toevoegen Kan onderliggende rij niet toevoegen: foreign key beperking gefaald Cannot delete or update a parent row: a foreign key constraint fails Fout bij opbouwen verbinding naar master: %-.128s Fout bij uitvoeren query op master: %-.128s Fout tijdens uitvoeren van commando %s: %-.128s Foutief gebruik van %s en %s De gebruikte SELECT commando's hebben een verschillend aantal kolommen Kan de query niet uitvoeren vanwege een conflicterende read lock Het combineren van transactionele en niet-transactionele tabellen is uitgeschakeld. Optie '%s' tweemaal gebruikt in opdracht Gebruiker '%-.64s' heeft het maximale gebruik van de '%s' faciliteit overschreden (huidige waarde: %ld) Toegang geweigerd. U moet het %-.128s privilege hebben voor deze operatie Variabele '%-.64s' is SESSION en kan niet worden gebruikt met SET GLOBAL Variabele '%-.64s' is GLOBAL en dient te worden gewijzigd met SET GLOBAL Variabele '%-.64s' heeft geen standaard waarde Variabele '%-.64s' kan niet worden gewijzigd naar de waarde '%-.200s' Foutief argumenttype voor variabele '%-.64s' Variabele '%-.64s' kan alleen worden gewijzigd, niet gelezen Foutieve 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 log Slave SQL thread negeerde de query vanwege replicate-*-table opties Variabele '%-.192s' is geen %s variabele Incorrecte foreign key definitie voor '%-.192s': %s Sleutel- en tabelreferentie komen niet overeen Operand behoort %d kolommen te bevatten Subquery retourneert meer dan 1 rij Onebekende prepared statement handler (%.*s) voor %s aangegeven Help database is beschadigd of bestaat niet Cyclische verwijzing in subqueries Veld '%s' wordt van %s naar %s geconverteerd Verwijzing '%-.64s' niet ondersteund (%s) Voor elke afgeleide tabel moet een unieke alias worden gebruikt Select %u werd geredureerd tijdens optimtalisatie Tabel '%-.192s' uit een van de SELECTS kan niet in %-.32s gebruikt worden Client ondersteunt het door de server verwachtte authenticatieprotocol niet. Overweeg een nieuwere MySQL client te gebruiken Alle delete van een SPATIAL index dienen als NOT NULL gedeclareerd te worden COLLATION '%s' is niet geldig voor CHARACTER SET '%s' Slave is reeds actief Slave is reeds gestopt Ongecomprimeerder data is te groot; de maximum lengte is %d (waarschijnlijk, de lengte van de gecomprimeerde data was beschadigd) ZLIB: Onvoldoende geheugen ZLIB: Onvoldoende ruimte in uitgaande buffer (waarschijnlijk, de lengte van de ongecomprimeerde data was beschadigd) ZLIB: Invoer data beschadigd Row %u was cut by GROUP_CONCAT() Rij %ld bevat niet de data voor alle kolommen Regel %ld ingekort, bevatte meer data dan invoer kolommen Column set to default value; NULL supplied to NOT NULL column '%s' at row %ld Out of range value for column '%s' at row %ld Data truncated for column '%s' at row %ld Using 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 users Can't revoke all privileges for one or more of the requested users Illegal 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 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 Field or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%d Incorrect parameter or combination of parameters for START REPLICA UNTIL 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 SQL thread is not to be started so UNTIL options are ignored Incorrect index name '%-.100s' Incorrect catalog name '%-.100s' Query cache failed to set size %lu; new query cache size is %lu Column '%-.192s' cannot be part of FULLTEXT index Unknown key cache '%-.100s' MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work Unknown storage engine '%s' '%s' is deprecated and will be removed in a future release. Please use %s instead The target table %-.100s of the %s is not updatable The '%s' feature is disabled; you need MySQL built with '%s' to have it working The MySQL server is running with the %s option so it cannot execute this statement Column '%-.100s' has duplicated value '%-.64s' in %s Truncated incorrect %-.64s value: '%-.128s' Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause Invalid ON UPDATE clause for '%-.192s' column This command is not supported in the prepared statement protocol yet Got error %d '%-.100s' from %s Got temporary error %d '%-.100s' from %s Unknown or incorrect time zone: '%-.64s' Invalid TIMESTAMP value in column '%s' at row %ld Invalid %s character string: '%.64s' Result of %s() was larger than max_allowed_packet (%ld) - truncated Conflicting declarations: '%s%s' and '%s%s' Can't create a %s from within another stored routine %s %s already exists %s %s does not exist Failed to DROP %s %s Failed to CREATE %s %s %s with no matching label: %s Redefining label %s End-label %s without match Referring to uninitialized variable %s PROCEDURE %s can't return a result set in the given context RETURN is only allowed in a FUNCTION %s is not allowed in stored procedures The 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 interrupted Incorrect number of arguments for %s %s; expected %u, got %u Undefined CONDITION: %s No RETURN found in FUNCTION %s FUNCTION %s ended without RETURN Cursor statement must be a SELECT Cursor SELECT must not have INTO Undefined CURSOR: %s Cursor is already open Cursor is not open Undeclared variable: %s Incorrect number of FETCH variables No data - zero rows fetched, selected, or processed Duplicate parameter: %s Duplicate variable: %s Duplicate condition: %s Duplicate cursor: %s Failed to ALTER %s %s Subquery value not supported %s is not allowed in stored function or trigger Variable or condition declaration after cursor or handler declaration Cursor declaration after handler declaration Case not found for CASE statement Configuration file '%-.192s' is too big Malformed 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 table File '%-.192s' has unknown type '%-.64s' in its header '%-.192s.%-.192s' is not %s Column '%-.192s' is not updatable View's SELECT contains a subquery in the FROM clause View's SELECT contains a '%s' clause View's SELECT contains a variable or parameter View'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 counts View merge algorithm can't be used here for now (assumed undefined algorithm) View being updated does not have complete key of underlying table in it View '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them Can't drop or alter a %s from within another stored routine GOTO is not allowed in a stored procedure handler Trigger already exists Trigger does not exist Trigger's '%-.192s' is view or temporary table Updating of %s row is not allowed in %strigger There is no %s row in %s trigger Field '%-.192s' doesn't have a default value Division by 0 Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ld Illegal %s '%-.192s' value found during parsing CHECK 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: %s Password hash should be a %d-digit hexadecimal number Target log not found in binlog index I/O error reading log index file Server configuration does not permit binlog purge Failed on fseek() Fatal error during log purge A purgeable log is in use, will not purge Unknown error during log purge Failed initializing relay log position: %s You are not using binary logging The '%-.64s' syntax is reserved for purposes internal to the MySQL server WSAStartup Failed Can't handle procedures with different groups yet Select must have a group with this procedure Can't use ORDER clause with this procedure Binary logging and replication forbid changing the global server %s Can't map file: %-.200s, errno: %d Wrong magic in %-.64s Prepared statement contains too many placeholders Key part '%-.192s' length cannot be 0 View text checksum failed Can not modify more than one base table through a join view '%-.192s.%-.192s' Can not insert into join view '%-.192s.%-.192s' without fields list Can not delete from join view '%-.192s.%-.192s' Operation %s failed for %.256s XAER_NOTA: Unknown XID XAER_INVAL: Invalid arguments (or unsupported command) XAER_RMFAIL: The command cannot be executed when global transaction is in the %.64s state XAER_OUTSIDE: Some work is done outside global transaction XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency XA_RBROLLBACK: Transaction branch was rolled back There is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s' Failed to grant EXECUTE and ALTER ROUTINE privileges Failed to revoke all privileges to dropped routine Data too long for column '%s' at row %ld Bad SQLSTATE: '%s' %s: ready for connections. Version: '%s' socket: '%s' port: %d %s Can't load value from file with fixed size rows to variable You are not allowed to create a user with GRANT Incorrect %-.32s value: '%-.128s' for function %-.32s Table definition has changed, please retry transaction Duplicate handler declared in the same block OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger Not allowed to return a result set from a %s Cannot get geometry object from data you send to the GEOMETRY field 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 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) 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 value Recursive 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 types Unable to connect to foreign data source: %.64s There was a problem processing the query on the foreign data source. Data source error: %-.64s The foreign data source you are trying to reference does not exist. Data source error: %-.64s Can't create federated table. The data source connection string '%-.64s' is not in the correct format The data source connection string '%-.64s' is not in the correct format Can't create federated table. Foreign data src error: %-.64s Trigger in wrong schema Thread 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 long Cannot drop default keycache Display width out of range for column '%-.192s' (max = %lu) XAER_DUPID: The XID already exists Datetime function: %-.32s field overflow Can'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 manner Not allowed to set autocommit from a stored function or trigger Definer is not fully qualified View '%-.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' definer The user specified as a definer ('%-.64s'@'%-.64s') does not exist Changing 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 renamed No 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 %.192s Failed 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 functions Can't create more than max_prepared_stmt_count statements (current value: %lu) `%-.192s`.`%-.192s` contains view recursion Non-grouping field '%-.192s' is used in %-.64s clause The used table type doesn't support SPATIAL indexes Triggers can not be created on system tables Leading spaces are removed from name '%s' Failed to read auto-increment value from storage engine user name host name String '%-.70s' is too long for %s (should be no longer than %d) The target table %-.100s of the %s is not insertable-into Table '%-.64s' is differently defined or of non-MyISAM type or doesn't exist Too high level of nesting for select Name '%-.64s' has become '' First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY The 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: %-.64s Table storage engine '%-.64s' does not support the create option '%.64s' Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partition Only %-.64s PARTITIONING can use VALUES %-.64s in partition definition MAXVALUE can only be used in last partition definition Subpartitions can only be hash partitions and by key Must define subpartitions on all partitions if on one partition Wrong number of partitions defined, mismatch with previous setting Wrong number of subpartitions defined, mismatch with previous setting Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed Expression in RANGE/LIST VALUES must be constant Field in list of fields for partition function not found in table List of fields is only allowed in KEY partitions The partition info in the frm file is not consistent with what can be written into the frm file The %-.192s function returns the wrong type For %-.64s partitions each partition must be defined VALUES LESS THAN value must be strictly increasing for each partition VALUES value must be of same type as partition function Multiple definition of same constant in list partitioning Partitioning can not be used stand-alone in query The mix of handlers in the partitions is not allowed in this version of MySQL For the partitioned engine it is necessary to define all %-.64s Too many partitions (including subpartitions) were defined It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning Failed to create specific handler file A BLOB field is not allowed in partition function A %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered). Number of %-.64s = 0 is not an allowed value Partition management on a not partitioned table is not possible Foreign keys are not yet supported in conjunction with partitioning Error in list of partitions to %-.64s Cannot remove all partitions, use DROP TABLE instead COALESCE PARTITION can only be used on HASH/KEY partitions REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs %-.64s PARTITION can only be used on RANGE/LIST partitions Trying to Add partition(s) with wrong number of subpartitions At least one partition must be added At least one partition must be coalesced More partitions to reorganize than there are partitions Duplicate partition name %-.192s It is not allowed to shut off binlog on this command When reorganizing a set of partitions they must be in consecutive order Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range Partition function not supported in this version for this handler Partition state cannot be defined from CREATE/ALTER TABLE The %-.64s handler only supports 32 bit integers in VALUES Plugin '%-.192s' is not loaded Incorrect %-.32s value: '%-.128s' Table has no partition for value %-.64s It is not allowed to specify %s more than once Failed to create %s Failed to drop %s The handler doesn't support autoextend of tablespaces A size parameter was incorrectly specified, either number or on the form 10M The size number was correct but we don't allow the digit part to be more than 2 billion Failed to alter: %s Writing one row to the row-based binary log failed Table definition on source and replica does not match: %s Replica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log events Event '%-.192s' already exists Failed to store event %s. Error code %d from storage engine. Unknown event '%-.192s' Failed to alter event '%-.192s' Failed to drop %s INTERVAL is either not positive or too big ENDS is either invalid or before STARTS Event execution time is in the past. Event has been disabled Failed to open mysql.event No datetime expression provided Column count of mysql.%s is wrong. Expected %d, found %d. The table is probably corrupted Cannot load from mysql.%s. The table is probably corrupted Failed to delete the event from mysql.event Error during compilation of event's body Same old and new event name Data for column '%s' too long Cannot drop index '%-.192s': needed in a foreign key constraint The syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s instead You can't write-lock a log table. Only read access is possible You can't use locks with log tables. Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entry 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. Cannot switch out of the row-based binary log format when the session has open temporary tables Cannot change the binary logging format inside a stored function or trigger The NDB cluster engine does not support changing the binlog format on the fly yet Cannot create temporary table with partitions Partition constant is out of partition function domain This partition function is not allowed Error in DDL log Not allowed to use NULL value in VALUES LESS THAN Incorrect partition name Transaction characteristics can't be changed while a transaction is in progress ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s' Internal scheduler error %d Error during starting/stopping of the scheduler. Error code %u Engine cannot be used in partitioned tables Cannot activate '%-.64s' log The server was not built with row-based replication Decoding of base64 string failed Recursion of EVENT DDL statements is forbidden when body is present Cannot proceed because system tables used by Event Scheduler were found damaged at server start Only integers allowed as number here This storage engine cannot be used for log tables You cannot '%s' a log table if logging is enabled 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' 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 %-.192s This function '%-.192s' has the same name as a native function Dubbele ingang '%-.64s' voor zoeksleutel '%-.385s' Too many files opened, please execute the command again Event 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: %s Table has no partition for some existing values Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s Fatal error: %s Relay log read failure: %s Relay log write failure: %s Failed to create %s Source command %s failed: %s Binary logging not possible. Message: %s View `%-.64s`.`%-.64s` has no creation context Creation context of view `%-.64s`.`%-.64s' is invalid Creation context of stored routine `%-.64s`.`%-.64s` is invalid Corrupted TRG file for table `%-.64s`.`%-.64s` Triggers for table `%-.64s`.`%-.64s` have no creation context Trigger creation context of table `%-.64s`.`%-.64s` is invalid Creation context of event `%-.64s`.`%-.64s` is invalid Cannot open table for trigger `%-.64s`.`%-.64s` Cannot create stored routine `%-.64s`. Check warnings Ambiguous replica modes combination. %s The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement. Corrupted replication event was detected Invalid column reference (%-.64s) in LOAD DATA Being purged log %s was not found XA_RBTIMEOUT: Transaction branch was rolled back: took too long XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected Prepared statement needs to be re-prepared DELAYED option not supported for table '%-.192s' The connection metadata structure does not exist <%-.64s> option ignored Built-in plugins cannot be deleted Plugin is busy and will be uninstalled on shutdown %s variable '%s' is read-only. Use SET %s to assign the value Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted Unexpected source's heartbeat data: %s The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds). Bad schema for mysql.ndb_replication table. Message: %-.64s Error in parsing conflict function. Message: %-.64s Write to exceptions table failed. Message: %-.128s Comment 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 Manual Database Table Partition Subpartition Temporary Renamed Too many active concurrent transactions Non-ASCII separator arguments are not fully supported debug sync point wait timed out debug sync point hit limit reached Duplicate condition information item '%s' Unhandled user-defined warning condition Unhandled user-defined not found condition Unhandled user-defined exception condition RESIGNAL when handler not active SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE Data 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-id Query cache is disabled; restart the server with query_cache_type=1 to enable it Duplicate partition field name '%-.192s' Inconsistency in usage of column lists for partitioning Partition column values of incorrect type Too many fields in '%-.192s' Cannot use MAXVALUE as value in VALUES IN Cannot have more than one value for this type of %-.64s partitioning Row expressions in VALUES IN only allowed for multi-field column partitioning Field '%-.192s' is of a not allowed type for this type of partitioning The total length of the partitioning fields is too large 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. %s 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. 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 Cannot 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: %s Column %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 transaction The 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 structure Invalid performance_schema usage. Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statement Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction Cannot change the binlog direct flag inside a stored function or trigger A SPATIAL index may only contain a geometrical type column Comment 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 clause Mixing 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 transaction Cannot change the sql_log_bin inside a stored function or trigger Failed to read from the .par file VALUES value for partition '%-.64s' must have type INT Toegang geweigerd voor gebruiker: '%-.48s'@'%-.64s' SET PASSWORD has no significance for users authenticating via plugins GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists Cannot truncate a table referenced in a foreign key constraint (%.192s) Plugin '%s' is force_plus_permanent and can not be unloaded 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. 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 again Primary 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 corrupted Undo 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 unsafe Table 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 corrupted The requested value %s for the source delay exceeds the maximum %u Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided) Non matching attribute '%-.64s' between partition and table Table to exchange with partition is partitioned: '%-.64s' Table to exchange with partition is temporary: '%-.64s' Subpartitioned table, use subpartition instead of partition Unknown partition '%-.64s' in table '%-.64s' Tables have different definitions Found a row that does not match the partition Option 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 long Replication 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 table Found a row not matching the given partition set partition '%-.64s' bestaat niet 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. %s The 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. %s FULLTEXT index is not supported for partitioned tables. Invalid condition number Sending 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 table Setting authentication options is not possible when only the Replica SQL Thread is being started. The table does not have FULLTEXT index to support this query The 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 time Cannot create FULLTEXT index on temporary InnoDB table Column '%-.192s' is of wrong type for an InnoDB FULLTEXT index Index '%-.192s' is of wrong type for an InnoDB FULLTEXT index Creating 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 corrupted Replica must silently retry current transaction There is a foreign key check running on table '%-.192s'. Cannot discard the table. Schema mismatch (%s) Table '%-.192s' in system tablespace IO Read error: (%lu, %s) %s IO Write error: (%lu, %s) %s Tablespace is missing for table %s. Tablespace '%-.192s' exists. Tablespace has been discarded for table '%-.192s' Internal error: %s ALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s' Index corrupt: %s Invalid display width. Use YEAR instead. Your password does not satisfy the current policy requirements You 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 tables Failed 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 NULL Duplicate 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 mode 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'. 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 lock Partition specific operations do not yet support LOCK/ALGORITHM Columns participating in a foreign key are renamed Cannot change column type INPLACE Adding foreign keys needs foreign_key_checks=OFF Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows Dropping a primary key is not allowed without also adding a new primary key Adding an auto-increment column requires a lock Cannot replace hidden FTS_DOC_ID with a user-visible one Cannot drop or rename FTS_DOC_ID Fulltext index creation requires a lock 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 Dubbele 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_MODE Your password has expired. To log in you must change it using a client that supports expired passwords. Found a row in wrong partition %s 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. Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table The binary log file '%s' is logically corrupted: %s file %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 values Row 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 repository Replica failed to initialize applier metadata structure from the repository Access 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 long Plugin '%s' cannot be uninstalled now. %s 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'. 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 corrupted 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' 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 table Foreign 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/REPLACE Invalid size for column '%-.192s'. Table storage engine '%-.64s' found required create option missing Out 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 first Cannot create FULLTEXT index on materialized subquery Undo Log error: %s Invalid argument for logarithm This 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 exceeded Select is not a read only statement, disabling timer Duplicate 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 INTERSECT Expression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated query 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. replica_preserve_commit_order is not supported %s. The server is currently in offline mode Binary 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 characters Incorrect 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 view Do not support online operation on table with GIS index User variable name '%-.100s' is illegal Cannot %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 %s Expression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %s Supplied filter list contains a value which is not in the required format 'db_pattern.table_pattern' OK packet too large Invalid JSON data provided to function %s: %s Invalid 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 %s Unsupported number of coordinate dimensions in function %s: Found %u, expected %u Replica 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' first This 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_by In aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_by Updating '%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 actions Cannot 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 error Unsupported MAX_EXECUTION_TIME MAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements only Hint %s is ignored as conflicting/duplicated Query block name %s is not found for %s hint Unresolved name %s for %s hint 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. Command not supported by pluggable protocols Incorrect 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 %.*s Version 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.%-.0s The JSON binary value contains invalid data. Invalid JSON path expression. The error is around character position %u.%-.200s Cannot 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 %ld Invalid JSON value for CAST to %s%-.0s from column %s at row %ld The 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 available Session was killed Memory capacity of %llu bytes for '%s' exceeded. %s Range optimization was not done for this query. Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONING The 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: %s Write 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; %s Can not perform keyring migration : %s Access denied; you need %-.128s privileges for this operation Keyring 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 operation SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user. Could not reinitialize audit log filters. Invalid argument type Invalid argument count audit_log plugin has not been installed using INSTALL PLUGIN syntax. Invalid "max_array_length" argument type. Invalid "max_array_length" argument value. %s Filter 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%s Grouping 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 name 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 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. KDF option size is invalid, please provide valid size < %d bytes and not NULL CREATE 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 - %.256s This storage engine does not support the %s index algorithm, storage engine default was used instead. Database '%-.192s' doesn't exist Too 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 length Aggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() function Hints 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 invisible Unknown authorization ID `%.64s`@`%.64s` Failed to grant %.90s` to %.90s Failed to open the security system tables Failed to set default roles Cannot 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 forbidden Cannot 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: %s Can 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 table system table table Invalid 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 UNION Recursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive ones Recursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query block 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 In 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=InnoDB Window 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 type Window '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal type Window '%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 BY To get information about window functions use EXPLAIN FORMAT=JSON Window function '%s' ignores the frame clause of window '%s' and aggregates over the whole partition Windowing 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 BY Comment 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 %s Variable %s does not exist in persisted config file Longitude %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 %s Access 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 function Unable 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 operation You 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 policy Non-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password history The client doesn't support %s Tablespace '%s' was skipped since its definition is being modified by concurrent DDL statement Engine '%.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' exists Resource Group '%-.192s' does not exist. Invalid cpu id %u Invalid VCPU range %u-%u Invalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d]. %s operation is disallowed on %s Resource 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. %s Failed 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 alias INNER 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 expiration Invalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object. Column '%-.192s' cannot be null 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. Create table/tablespace '%-.192s' failed, as disk is full Could 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 exist Failed 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 expected Unable 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 again 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. 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 %ld Value is out of range for functional index '%s' at row %ld Cannot 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 index Cannot 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 specified Cannot 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 clauses GRANT ... 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' argument Redo log archiving start timed out Server variable 'innodb_redo_log_archive_dirs' is NULL or empty Label '%.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 directory Redo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s' Redo log archive directory '%.192s' is accessible to all OS users Cannot create redo log archive file '%.512s' (OS errno: %d - %.128s) Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() first Redo log archiving is not active Redo log archiving failed: %.512s Redo log archiving has not been started by this session Regex 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 %s Column '%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: %.512s Clone 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. %s Empty 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': %s Storage engine could not allocate temporary tablespace for this session. Got unknown error: %d Could 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: %s Secondary 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. %s Cannot update GTID_PURGED with the Group Replication plugin running Grouping 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 %lu A 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 mandatory Failed to acquire lock on user management service, unable to fetch mandatory role list Loading local data is disabled; this must be enabled on both the client and server sides Failed to import %s because the CFG file version (%u) is not compatible with the current version (%u) Out of memory Character 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 %u Failed 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 first 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. 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' on 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. Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200s Only 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 %.128s Invalid json attribute, error: "%s" at pos %u: '%s' Storage engine '%s' does not support ENGINE_ATTRIBUTE. The user attribute must be a valid JSON object Cannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCE Cannot 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 RETURNING The function %s does not support the character set '%s'. Conversion from collation %s into %s impossible for %s Schema '%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%s User %.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 type Reads 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_name 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. 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 %uM InnoDB: "%s" not allowed with general tablespaces AUTOEXTEND_SIZE value should be between %uM and %uM AUTOEXTEND_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 loop A table must have at least one visible column. Compression failed with the following error : %s The 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_uuid Unable 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 ignored 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. 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 type 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. 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. %s Comment 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=ON Maximum 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. %s Using %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 group Invalid timestamp format in %s udf SHAPE_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: %s Bulk executor error: %s Bulk reader failed to initialize libcurl Bulk reader got libcurl error: %s Bulk reader got error response from server: %ld Bulk 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: %s The first file being loaded contained less lines than the ignore clause Missing 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: %s 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' 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 null The 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. %s Parser saw: %s Can't create thread to handle bootstrap (errno: %d) Trigger for table '%s'.'%s': invalid %s value (%s). Wrong tree: %s Error: Invalid %s Skip re-populating collations and character sets tables in %s%sread-only mode. Using data dictionary with version '%d'. Installed data dictionary with version %d Data 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" or Failed to write to %s: %s 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). 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 exit View '%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.%s Unable 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 deleted Error: Unable to create primary object key Error: Unable to create object key Can'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: %22s Debug sync points executed: %22s Debug sync points max active per thread: %22s Debug Sync Facility disabled due to lack of memory. Can't init tc log Event Scheduler: Can't initialize the execution queue Event Scheduler: Purging the queue. %u events Event Scheduler: Last execution of %s.%s. %s %*s Event Scheduler: [%s].[%s.%s] event execution failed. Event Scheduler: Cannot initialize the scheduler thread Event Scheduler: Stopped Event scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d) Event Scheduler: Waiting for the scheduler thread to reply Event Scheduler: scheduler thread started with id %u Event Scheduler: Serious error during getting next event to execute. Stopping Event_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event scheduler Event Scheduler: Killing the scheduler thread, thread id %u IP address '%s' could not be resolved: %s Host name '%s' could not be resolved: %s IP 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: - %s Definer 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.%s Failed to bootstrap components infrastructure. Failed to shutdown components infrastructure. Failed to bootstrap persistent components loader. Giving %d client threads a chance to die gracefully CA certificate %s is self signed. Failed to set up SSL because of the following SSL library error: %s Failed 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: %llu The 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: %s Unsupported value 0 for secure-auth Invalid 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 set net_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 handling Could not allocate memory for thread handling Can't create test file %s Can't start server: can't create PID file: %s Unable to delete pid file: %s Can'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 : %s Ignoring --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 disabled Insecure 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-priv Insecure 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 %d Can'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 signals Wrong date/time format specifier: %s Could not allocate replication and binlog filters: %s Cannot allocate the keycache Current 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 system Iteration %d: Current time obtained from system is greater than 2038 This MySQL server doesn't support dates later then 2038 %s (mysqld %s) starting as process %lu Shutting down replica threads Forcefully disconnecting %d remaining clients Aborting Binlog end gethostname failed, using '%s' as hostname One can only use the --user switch if running as root Fatal 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: %s setuid: %s setregid: %s setreuid: %s chroot: %s TCP/IP, --shared-memory, or --named-pipe should be configured on NT OS CTRL-C ignored during startup '%s' can not be used as client character set. '%s' will be used as default client character set. Out of memory Failed to lock memory. Errno: %d my_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 line Could 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 file Can't init databases There 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 files Bad 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: %s 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. Setting lower_case_table_names=2 because file system for %s is case insensitive 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. You need to use --log-bin to make %s work. Path '%s' is a directory name, please specify a file name for %s option 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. 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 Unable 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 %ld failed to set datadir to %s Can't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/group Can't change data directory owner to %s Setting 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-plugin Could not join %sthread. error:%d An error occurred while building do_table and ignore_table rules to hashes for global replication filter. Error opening CA certificate file Error accessing directory pointed by --ssl-capath Found %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 available Could not open file '%s' for error logging%s%s Invalid 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 %s Unable 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.%s Resolving 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' failed mysql_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: %c Failed 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 file VALGRIND_DO_QUICK_LEAK_CHECK VALGRIND_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: %d Can't allocate memory for udf structures Can'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 %s Found %d prepared XA transactions ignore xid %s commit xid %s rollback xid %s Starting 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 %s 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 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 Table '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table! Got an error from thread_id=%u, %s:%d Got an error from unknown thread, %s:%d Too many storage engines! Storage engine '%s' has conflicting typecode. Assigning value %d. Out of memory on transaction write set extraction Unable to allocate memory for plugin '%s' handlerton. Shared memory setting up listener Can't create shared memory service: %s. : %s Can't create shared memory connection: %s. : %s Can't create event, last error=%u Can't create new named pipe!: %s Can'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: %d IPv6 is available. IPv6 is not available. Can't create IP socket: %s Can'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 %u Can't start server: Bind on TCP/IP port: %s Fails to print out IP-address. - '%s' resolves to '%s'; Can't start server: listen() on TCP/IP port: %s listen() on TCP/IP failed with error %d The socket file path is too long (> %u): %s Unable to setup unix socket lock file. Can't start server: UNIX Socket : %s Can't start server : Bind on unix socket: %s listen() on Unix socket failed with error %d Unable 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 select Error in accept: %s RSA %s key file not found: %s. Some authentication plugins will not work. Failure to parse RSA %s key (file exists): %s: %s Failure to read key file: %s RSA 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: %s X.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 %s Could not generate RSA private key required for X.509 certificate. Could not write key file: %s Could not set file permission for %s Could not read CA key file: %s Could not read CA certificate file: %s Could not generate X.509 certificate. Could not write certificate file: %s Could not generate RSA Private/Public key pair Could not write private key file: %s Could not write public key file: %s Skipping 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: %s Fatal: 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 Engine Found 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 upgrade Can'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 changed Found wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it! Unable to open file %s Error in reading file %s Table '%s' was created with a different version of MySQL and cannot be read Unable to read view %s File %s has unknown type in its header. Incorrect information in file %s Can't open and lock privilege tables: %s Plugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported. Plugin '%s' has invalid data. Fatal error: OOM while initializing time zones Can't open and lock time zone table: %s trying to live without them Fatal error: Out of memory while loading mysql.time_zone_leap_second table Fatal error: While loading mysql.time_zone_leap_second table: too much leaps Fatal error: Error while loading mysql.time_zone_leap_second table Fatal 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 id Error while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviations Error while loading time zone description from mysql.time_zone_transition_type table Error while loading time zone description from mysql.time_zone_transition table: too much transitions Error while loading time zone description from mysql.time_zone_transition table: bad transition type id Error while loading time zone description from mysql.time_zone_transition table loading time zone without transition types Out of memory while loading time zone description Unable to build mktime map for time zone Out of memory while loading time zone Fatal error: Out of memory while setting new time zone Replica SQL thread is stopped because UNTIL condition is bad(%s:%llu). Replica SQL thread stopped because it reached its UNTIL position %llu Replica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already applied Replica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %s Replica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %s Replica 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:%d Can't start server : Initialize security descriptor: %s Can't start server : Set security descriptor: %s Can'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 : %llu 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. 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.%s NDB Replica: Table %s.%s : %s, low epoch resolution Found unexpected field type %u Failed to create NdbInfo Failed to init NdbInfo ndb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u %s - %s.%s %s Info 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 %lu Transaction 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 TABLE For the creation of replication channels the server id must be different from 0 Replica: Wrong repository. Repository should be TABLE Error 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: %s Replica: Could not create channel list 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. 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%s Replica: 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 table Invalid value for cost constant "%s" in mysql.server_cost table: %.1f Unknown cost constant "%s" in mysql.engine_cost table Unknown storage engine "%s" in mysql.engine_cost table Invalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost table Invalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1f Error while reading from mysql.server_cost table. Error while reading from mysql.engine_cost table. Failed to open optimizer cost constant tables Unsupported 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.%s Event Scheduler: Dropping %s.%s Ndb schema[%s.%s]: %s 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. root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option. A temporary password is generated for root@localhost: %s Failed to open the bootstrap file %s Bootstrapping 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 %s Start binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu) source sends heartbeat message the 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 them NDB: Query '%s' failed, error: %d: %s Killing thread %lu Plugin %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 %s Failed to decrement the number of threads Plugin %s did not deinitialize %u threads Killed %u threads of plugin %s NDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %s NDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica start NDB: NodeID is %lu, management server '%s:%lu' tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%u NDB Internal error: Default values differ for column %u, ndb_default: %d NDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%u field[ 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) failure NDB 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(): %s found uncommitted autocommit+rbwr transaction, commit status: %d Ndb replica retried transaction %u time(s) in vain. Giving up. Error %lu in ::update_create_info(): %s NDB: allocating table share for %s failed NDB Binlog: (%d)%s NDB Binlog: CREATE TABLE Event: %s NDB Binlog: FAILED CREATE TABLE event operations. Event: %s NDB Binlog: RENAME Event: %s NDB Binlog: FAILED create event operations during RENAME. Event %s Unexpected rename case detected, sql_command: %d Error %lu in ::get_auto_increment(): %s Calling ndbcluster_create_binlog_setup(%s) in ::open table '%s' opened read only NDB: '--initialize' -> ndbcluster plugin disabled NDB: Changed global value of binlog_format from STATEMENT to MIXED NDB_SHARE: trailing share %s, released by close_cached_tables NDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak. handle_trailing_share: %s use_count: %u ndbcluster_get_share: %s use_count: %u ndbcluster_real_free_share: %s use_count: %u ndbcluster_real_free_share: %s, still open - ignored 'free' (leaked?) ndbcluster_free_share: %s use_count: %u ndbcluster_mark_share_dropped: %s use_count: %u ndbcluster_mark_share_dropped: destroys share %s Could not allocate Thd_ndb object NDB Binlog: Ndb tables initially read only. ndb util thread: malloc failure, query cache not maintained properly Trying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignored Trying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %s dbug_check_shares open: %s.%s: state: %s(%u) use_count: %u dbug_check_shares dropped: Invalid (old?) table or database name '%s' Recovering after a crash using %s Cannot perform automatic crash recovery when --tc-heuristic-recover is used Bad magic header in tc log Recovery failed! You must enable exactly %d storage engines that support two-phase commit protocol 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} Heuristic crash recovery mode Heuristic crash recovery failed Please restart mysqld without --tc-heuristic-recover Failed 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 discontinued Replica: Could not stop replica for channel '%s' operation discontinued Error during --relay-log-recovery: Could not locate rotate event from the source. Error during --relay-log-recovery: Error reading events from relay log: %d Error during --relay-log-recovery: Error while freeing IO_CACHE object Relay log recovery skipped for group replication channel. Error during --relay-log-recovery: %s Error 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%s Can'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 secs Error 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 %s 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 Replica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu. Error initializing relay log position%s: %s Replica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %s Replica I/O thread%s killed while connecting to source Replica I/O thread couldn't register on source Forcing to reconnect replica I/O thread%s Failed on request_dump()%s 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 Stopping replica I/O thread due to out-of-memory error from source Replica I/O thread aborted while waiting for relay log space Replica I/O thread exiting%s, read up to log '%s', position %s Failed during replica worker initialization%s 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 Error 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_period Failed during replica worker thread creation%s Failed during replica worker thread creation%s (errno= %d) Failed to init partitions hash Replica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value Replica 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-%06d Replica: %s Error_code: MY-%06d 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 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 Replica SQL thread%s exiting, replication stopped in log '%s' at position %s Read invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bug The 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 %s next log '%s' is active next log '%s' is not active Replica 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) failed NDB: 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 distributed NDB: Creating %s.%s NDB: Flushing %s.%s NDB: Cleaning stray tables from database '%s' NDB: Discovered missing database '%s' NDB: Discovered remaining database '%s' NDB: ndbcluster_find_all_databases retry: %u - %s NDB: ndbcluster_find_all_databases fail: %u - %s NDB: skipping setup table %s.%s, in state %d NDB: failed to setup table %s.%s, error: %d, %s NDB: missing frm for %s.%s, discovering... NDB: mismatch in frm for %s.%s, discovering... ndb_binlog_setup: Clean up leftovers NDB %s: waiting max %u sec for %s %s. epochs: (%u/%u,%u/%u,%u/%u) injector proc_info: %s NDB %s: waiting max %u sec for %s %s. epochs: (%u/%u,%u/%u,%u/%u) injector proc_info: %s map: %x%08x NDB %s: distributing %s timed out. Ignoring... NDB %s: not waiting for distributing %s NDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08x NDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete! NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08x NDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08x NDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08x NDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %d NDB: unknown value for binlog signalling 0x%X, %s not logged NDB: reply to %s.%s(%u/%u) from %s to %x%08x NDB: Could not release slock on '%s.%s', Error code: %d Message: %s NDB schema: Could not find table '%s.%s' in NDB NDB: 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%08x NDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: handling online alter/rename NDB Binlog: Failed to re-open shadow table %s.%s NDB Binlog: handling online alter/rename done NDB 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 privileges NDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08x NDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%s NDB 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_index NDB Binlog: Injecting random write failure NDB 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 - %s NDB 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 shutdown 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 NDB: server id provided is too large to be represented in opt_server_id_bits or is reserved NDB: --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_WRITE NDB Binlog: %s %s %s NDB Replica: Table %s.%s : Parse error on conflict fn : %s NDB Replica: Table %s.%s : %s NDB Binlog: Failed to get table %s from ndb: %s, %d NDB Binlog: NOT logging %s NDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %s NDB Binlog: CREATE (DISCOVER) TABLE Event: %s NDB Binlog: DISCOVER TABLE Event: %s NDB Binlog: logging of table %s with BLOB attribute and no PK is not supported NDB Binlog: Unable to create event in database. Event: %s Error Code: %d Message: %s NDB Binlog: Unable to create event in database. Attempt to correct with drop failed. Event: %s Error Code: %d Message: %s NDB Binlog: Unable to create event in database. Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %s NDB Binlog: discover reusing old ev op NDB Binlog: Creating NdbEventOperation failed for %s NDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %s NDB Binlog: ndbevent->execute failed for %s; %d %s NDB Binlog: logging %s (%s,%s) NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %s NDB %s: %s timed out. Ignoring... NDB Binlog: unhandled error %d for table %s NDB 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: %u NDB: Could not get apply status share NDB 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 binlog NDB Binlog: starting log at epoch %u/%u NDB Binlog: ndb tables writable NDB Binlog: Server shutdown detected... NDB Binlog: Just lost schema connection, hanging around NDB Binlog: ...and on our way NDB: error %lu (%s) on handling binlog schema event NDB Binlog: Failed to inject apply status write row NDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %d NDB Binlog: Error during COMMIT of GCI. Error: %d NDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%u NDB Binlog: Release extra share references NDB Binlog: remaining open tables: %s.%s state: %u use_count: %u Wrong tree: Parent doesn't point at parent Wrong tree: Root should be black Wrong tree: Found two red in a row Wrong tree: Found right == left Wrong tree: Incorrect black-count: %d - %d Use_count: Wrong count %lu for origin %p Use_count: Wrong count for key at %p, %lu should be %lu Wrong number of elements: %u (should be %u) for tree at %p Error reading replica worker configuration Error writing replica worker configuration Failed to open relay log %s, error: %s Error when worker read relay log events,relay log name %s, position %llu Failed to find next relay log when retrying the transaction, current relay log is %s Multi-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 log When opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary log Couldn't repair table: %s.%s Could not remove temporary table: '%s', error: %d System 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 deinitialization Plugin '%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 long Plugin '%s' will be forced to shutdown Plugin '%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 flag Missing 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 variables Setting persistent options for plugin '%s' failed. Failed on my_net_write, writing to stderr instead: %s Retrying repair of: '%s' without quick Retrying repair of: '%s' with keycache Found %s of %s rows when repairing '%s' Warning: Optimize table got errno %d on %s.%s, retrying Warning: Enabling keys got errno %d on %s.%s, retrying Checking table: '%s' Recovering table: '%s' Error in creating TABLE_SHARE from %s.frm file. Unable to acquire lock on %s.%s Error in allocation memory for TABLE object. Error in creating handler object for table %s.%s Error in setting handler reference for table %s.%s Unable to acquire lock on tablespace name %s Error in processing generated columns for table %s.%s Error in Creating DD entry for %s.%s Error in fetching %s.%s table data from dictionary Error in fixing SE data for %s.%s Error 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.%s Failed 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 failed Failed to set path %s Failed to open dir %s NDB: 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 %u NDB: failed to allocate global ndb cluster connection NDB: failed to allocate global ndb object NDB[%u]: using nodeid %u NDB[%u]: failed to allocate cluster connect object NDB[%u]: starting connect thread NDB[%u]: NodeID: %d, %s NDB[%u]: failed to start connect thread NDB: error (%u) %s Ignored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs provided Event 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 corrupted Unable to obtain lock for dropping event %s from schema %s Unable to drop event %s from schema %s Server 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 file file %s was not purged because it was being read by thread number %u I/O error reading the header from the binary log, errno=%d, io cache code=%d Failed 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: %d Read %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 files Failed 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 file MYSQL_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 read MYSQL_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 files Failed to delete file '%s' and read the binlog index file Failed 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 %s Failed 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' hooks 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} The following warning was suppressed %d times during the last %d seconds in the error log NDB: %s NDB %s: %s NDB: Unable to purge %s.%s File=%s (failed to setup thd) Unknown collation #%lu. syntax error in innodb_log_group_home_dir syntax error in innodb_undo_directory InnoDB: 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 %lf InnoDB: 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 active MySQL 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:%lu Cannot 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 failed Table %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: %s 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 Command '%s' cannot be aborted. The trigger error was (%d) [%s]: %s Event '%s' cannot be aborted. The trigger error was (%d) [%s]: %s %s. The trigger error was (%d) [%s]: %s Replica SQL: Configuration with number of replication sources = %u' is not supported when applying to Ndb Replica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to Ndb NDB %s: distributing %s err: %u 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. 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 context 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. 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 space Out 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 %s Failed 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: %s The 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. %s Binary 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 small Mecab 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 %d Source server does not support semi-sync, fallback to asynchronous replication Set 'rpl_semi_sync_replica=1' on source failed Failed to stop ack receiver thread on my_thread_join, errno(%d). Failed to read the firewall tables Failed to register dynamic privileges Statement was truncated and not recorded: %s Statement with no text was not recorded SUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %s ACCESS DENIED for '%s'. Reason: %s Statement: %s Skipped unknown user mode '%s' Reloading cache from disk FIREWALL RESET for '%s' Counters are reset to zero %s 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. 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. %s Error 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 exists Invalid 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 specified Dictionary file not loaded Dictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loaded Exception while reading the dictionary file Can't retrieve the %s from the security context Can't retrieve the security context Effective value of validate_password_length is changed. New value is %d %s Rewritten query failed to parse:%s Startup failed with error "%s" Exiting Exit done Using SSL configuration from MySQL Server Using SSL configuration from Mysqlx Plugin Neither MySQL Server nor Mysqlx Plugin has valid SSL configuration Using %s for TLS connections For more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation %s Failed to parse stored authentication string for %s. Please check if mysql.user table not corrupted Error in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problem Authentication requires either RSA keys or SSL encryption RSA key cipher length of %u is too long. Max value is %u Failed to open the %s filter tables Failed to open '%s.%s' %s table %s %s %s Password salt for user '%s' is corrupt Out 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 statistics This option cannot be set %s. The table '%-.192s' may not be created in the reserved tablespace '%-.192s'. SSL fips mode error: %s init_connect variable is ignored for user: %s host: %s due to expired password. sql_mode=0x%08x is not supported Out 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_coordinator Failed to update connection delay triggered stats Failed to reset connection delay triggered stats Unexpected option type for connection delay. Failed to initialize Connection_delay_action Could 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: %s Detected %u hanging client(s) Error accepting client Internal error scheduling client for execution Preparation of I/O interfaces failed, X Protocol won't be accessible srv_session_init_thread returned error Unable 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: %s Exception in post: %s Internal error scheduling task Exception in event loop: "%s": %s Setup of %s failed, %s %s Failed 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 %i Message is not properly initialized: %s Unable to set minimal number of workers to %u; actual value is %i Unable to accept connection, disconnecting client All 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 body client_id:%s - %s while reading from socket, closing connection %s.%u: Invalid authentication method %s %s: Unexpected message of type %i received during authentication Error writing to client: %s (%i) Scheduler "%s" started. Scheduler "%s" stopped. Please see the MySQL documentation for '%s' system variables to fix the error X Plugin ready for connections. %s Retrying `bind()` on TCP/IP port %i Shutdown triggered by mysqld abort flag Using %s account for authentication which has all required permissions Using existing %s account for authentication. Incomplete grants will be fixed Server starts handling incoming connections Stopped handling incoming connections %s: Could not interrupt client session %s: release triggered by timeout in state:%i IPv6 is available UNIX socket not configured Kill client: %i %s Could not get security context for session Unable to switch security context to root Error closing SQL session Error executing admin command %s: %s Error executing empty admin command Unable to retrieve system variable '%s' Unable to get creation stmt for collection '%s'; query result size: %lu Unable to get engine info for collection '%s'; creation stmt: %s Error getting result data: %s Capability expired password failed with error: %s Failed to set SO_REUSEADDR flag (error: %d). Could not open internal MySQL session Unable to switch context to user %s Can't unregister '%s' user defined function %s: get peer address failed, can't resolve IP to hostname Capability client interactive failed with error: %s Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only. Invalid key type Invalid key length for given block cipher Could not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets provided 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 keyring_file initialization failure due to internal exception inside the plugin. Failed to generate a key due to internal exception inside keyring_file plugin Error while %s key: invalid key_type Error while %s key: key_id cannot be empty Failed to %s due to internal exception inside %s plugin Incorrect Keyring file Found malformed keyring backup file - removing it Error while restoring keyring from backup file cannot overwrite keyring with backup Error while flushing in-memory keyring into keyring file Error while reading stat for %s.Please check if file %s was not removed. OS returned this error: %s Could not remove file %s OS retuned this error: %s Could not truncate file %s. OS retuned this error: %s Unknown error %d keyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path %s Error while loading keyring content. The keyring might be malformed Could not flush keys to keyring Could not flush keys to keyring's backup Error while fetching key: key_id cannot be empty Error while removing key: key_id cannot be empty 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 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. keyring_okv initialization failure due to internal exception inside the plugin Invalid key type Invalid key length for given block cipher Failed to generate a key due to internal exception inside keyring_okv plugin Could not find entry for server in configuration file %s Could not find entry for standby server in configuration file %s Could not parse the %s file provided Could not load keys' uids from the OKV server Could not initialize ssl layer Could not initialize OKV client Could not connect to the OKV server Could not remove the key Could not add attribute, attribute_name=%s attribute value=%s Could not generate the key. Could not store the key. Could not activate the key. Could not fetch generated key Could not store/generate the key - failed to set key attribute x-key-ready Could not retrieve key signature from custom attributes Could not retrieve key from OKV Error loading trust store Error setting the certificate file. Error setting the key file. Private key does not match the certificate public key Incorrect Keyring file Keyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value. Found malformed keyring backup file - removing it Error while restoring keyring from backup file cannot overwrite keyring with backup Error while flushing in-memory keyring into keyring file Keyring_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 path Could not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets provided The 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 plugin Failed to generate a key due to internal exception inside keyring_encrypted_file plugin 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. 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: %s Could not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %s Could not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %s Path to keyring aws configuration file cannot be empty Path 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 Server keyring_aws_cmk_id has to be set Could not get AWS KMS credentials from the configuration file keyring_aws initialization failure. keyring_aws initialization failure due to internal exception inside the plugin Invalid key length for given block cipher Failed to generate a key due to internal exception inside keyring_file plugin Incorrect Keyring file Found malformed keyring backup file - removing it Error while restoring keyring from backup file cannot overwrite keyring with backup Error while flushing in-memory keyring into keyring file Wrong region Could not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %s Could not generate a new key. AWS KMS returned this error: %s Could not encrypt key. AWS KMS returned this error: %s Could not re-encrypt key. AWS KMS returned this error: %s Could not decrypt key. AWS KMS returned this error: %s Could not rotate the CMK. AWS KMS returned this error: %s The 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. %s Error 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: %s Primary server with address %s left the group. Electing new Primary. Members joined the group: %s There 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. %s Unable to disable super read only flag. Try to disable it manually Unable 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: %s 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. 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. %s Detected 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 thread Failed to stop the group replication applier thread. Failed to fetch transaction data containing required transaction info for applier 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. 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 %lu auto_increment_offset is reset to %lu group_replication_auto_increment_increment is set to %lu auto_increment_offset is set to %lu Failed to fetch transaction context containing required transaction info for certification Failed to fetch Format_description_log_event containing required server info for applier Failed to fetch Transaction_context_log_event containing required transaction info for certification Failed to read snapshot version from transaction context event required for certification Failed to fetch Gtid_log_event containing required transaction info for certification Unable to update certification result on server side, thread_id: %lu Unable to add gtid information to the group_gtid_executed set when gtid was provided for local transactions Unable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactions Failed to notify certification outcome Unable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactions Unable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactions Failed to fetch View_change_log_event containing required info for certification Error when contacting the server to ensure the proper logging of a group change in the binlog Timeout when waiting for the server to execute local transactions in order assure the group change proper logging Failed to fetch Log_event containing required server info for applier 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. Failed to establish an internal server connection to execute plugin operations Setting super_read_only=ON. Setting super_read_only=OFF. killed session id: %d status: %d killed failed id: %d failed: %d Internal query: %s result in error. Error number: %ld Error copying from empty string Query execution resulted in failure. errno: %d Unable to create a session for executing the queries on the server The member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connection Maximum 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/%d Retrying group recovery connection with another donor. Attempt %d/%d No valid donors exist in the group, retrying Error 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 threads Terminating existing group replication donor connection and purging the corresponding logs. Error when stopping the group replication incremental recovery's donor connection Error when purging the group replication recovery's relay logs Unable 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 hash Base 64 encoding of the write identification hash failed Binlog format should be ROW for Group Replication binlog_checksum should be NONE for Group Replication A transaction_write_set_extraction algorithm should be selected when running Group Replication Transaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group Replication Transaction 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 plugin Transaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the plugin We can only use one cache type at a time on session %u Failed to reinit binlog cache log for read on session %u Failed to create the context of the current transaction on session %u Failed to extract the set of items written during the execution of the current transaction on session %u Failed to gather the set of items written during the execution of the current transaction on session %u Error 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 %u Error while appending data to an internal cache on session %u Error while writing to transaction message on session %u Unable to register for getting notifications regarding the outcome of the transaction on session %u Error broadcasting transaction to the group on session %u. Message is too big. Error while broadcasting the transaction to the group on session %u Error while waiting for conflict detection procedure to finish on session %u Error while re-initializing an internal cache, for write operations, on session %u Failed to create group replication commit cache on session %u Failed to reinit group replication commit cache for write on session %u A previous recovery session is still running. Please stop the group replication plugin and wait for it to stop Fatal 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. %s Unable 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 group Error when processing certification information in the incremental recovery process Unable 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 service This 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 start Could not enable the server read only mode and guarantee a safe recovery execution Error on group communication engine initialization Can't start group replication on secondary member with single-primary mode while asynchronous replication channels are running. Error on group communication engine start Timeout on wait for view after joining group Error calling group communication interfaces Member 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 modification 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 Requesting to leave the group despite of not being a member Plugin '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 details On shutdown there was a timeout on the Group Replication applier termination. Unexpected failure while shutting down registry module! Failure during Group Replication handler initialization Failure when registering the server state observers Failure when registering the transactions state observers Failure when registering the binlog state observers Unable to start Group Replication on boot Failure when stopping Group Replication on plugin uninstall Failure when unregistering the server state observers Failure when unregistering the transactions state observers Failure when unregistering the binlog state observers All Group Replication server observers have been successfully unregistered Unable 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 abort Group communication SSL configuration: group_replication_ssl_mode: "%s" Unable to initialize the group communication engine Binlog must be enabled for Group Replication Gtid mode should be ON for Group Replication LOG_REPLICA_UPDATES should be ON for Group Replication 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. Applier metadata repository must be set to TABLE Connection 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: %s The group_replication_group_name option is mandatory The group_replication_group_name '%s' is not a valid UUID, its length is too big The group_replication_group_name '%s' is not a valid UUID group_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quota group_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quota group_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quota The given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limit There is one group_replication_force_members operation already ongoing group_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachable 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' Unknown group replication applier pipeline requested Unable to bootstrap group replication event handling infrastructure. Unknown handler type: %d One of the group replication applier handlers is null due to an initialization error A 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 initialization Error when initializing a session thread for internal server connection. Error running internal SQL query: %s. The internal server communication session is not initialized Error 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 operating Error 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: %s 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. 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: %s Failure in group communication engine '%s' initialization Unable to set the group communication engine logger Current debug options are: '%s'. Some debug options in '%s' are not valid. Error calling group communication interfaces while trying to leave the group Member is not ONLINE, it is not possible to force a new group membership Error calling group communication interfaces Error setting group_replication_force_members value '%s' on group communication interfaces The group_replication_force_members value '%s' was set in the group communication interfaces Timeout on wait for view after setting group_replication_force_members value '%s' into group communication interfaces Broadcast of committed transactions message failed. Message is too big. Error while sending stats message 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 Flow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lld Unable to convert a packet into an event on the applier. Error: %s Failed 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: %s Failed 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. %s The 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 Failed Skipping group search, No group attribute mentioned Pool max size is 0, connection pool is disabled Connection pool initialization, failed to create LDAP object creator Connection pool initialization, failed to create LDAP object LDAP TLS configuration LDAP TLS connection LDAP pool is not created. LDAP pool is initializing LDAP pool is de-initializing Pool max size old and new values are 0 LDAP pool is re-initializing Plug-in has failed to write the packet. Setting LDAP user name as : %s User authentication data: %s size: %lu User is authenticated as: %s external user: %s Group search information base DN: %s scope: %d filter: %s attribute: %s Special handling for group search, {GA} found Group search special handling, group full DN found. User %s is not member of any group. User %s is member of more than one group For user %s has multiple user group names. Please check if group attribute name is correct Searched group name: %s LDAP authentication object creation time_stamp: %s dn: %s Certificate name: %s Failed to pool de-initialized: pool is already reconstructing Pool initialization failed: pool is already initialized Pool initialization failed: pool is initializing Pool initialization failed: pool is de-initializing Failed to pool deinitialized: pool is already reconstructing Failed to pool deinitialized : pool is not ready Ldap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializing Connection pool has failed to initialized Ldap_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 client Ldap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the pool Ldap_authentication::search_user_group no group attribute found Ldap_connetion_pool::put ldap info null Ldap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the pool Ldap_connection_creator::Ldap_connection_creator starting TLS Ldap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info) Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %s Ldap_connection_pool::get create connection key: %s LDAP communication host %s port %u Sending authentication method to client : %s SASL request received from mysql client: %s Ldap_sasl_authentication::process_sasl rc: %s Ldap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %s LDAP authentication started for user name: %s %s LDAP authentication initialize is failed with: %s LDAP authentication failed or group retrieval failed: %s Search user group has failed: %s LDAP user bind has failed: %s Connection pool get: Failed to create LDAP connection. %s Failed to create new LDAP connection: %s Failed to establish TLS connection: %s Failed to search user full dn: %s Ldap_connection_pool::reinit 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. 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: %s validate_password status variables registration failed. validate_password status variables unregistration failed. Dictionary file open failed given password string could be null failed to convert the password string to lower case failed to convert the password string into a buffer memory allocation failed for string handler Since the validate_password_policy is mentioned as Strong, dictionary file must be specified convert_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 %s Failed 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 %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s Waited 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 %s Table 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 %zu Cannot close file %s, because modification count %lld != flush count %lld Cannot close file %s, because it is in use Open file list len in shard %zu is %llu Tablespace %s, waiting for IO to stop for %lld seconds %s %s %s %s %s 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. Max tablespace id is too high, %lu Trying to access missing tablespace %lu Trying 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. %s Cannot delete tablespace %lu because it is not found in the tablespace memory cache. While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %s Cannot delete tablespace %lu in DISCARD TABLESPACE: %s Cannot 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 resume Cannot find tablespace for '%s' in the tablespace memory cache Cannot find tablespace for '%s' in the tablespace memory cache Tablespace '%s' is already in the tablespace memory cache Cannot 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' failed Could not find a valid tablespace file for `%s`. %s Ignoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID %s %s %s %s Can'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 %s 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. %s %s %s %s %s %s %s %s %s %s %s %s %s Scan 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 %s A 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 %s Cannot 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 %s Blocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s). %s %s Blocked 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 %s The 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. %s Redo 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: %llu Flush overwriting data to archive - wait too long (1 minute) lag LSN: %llu %s Starting shutdown... Waiting for %s to exit Waiting for %lu active transactions to finish Waiting for master thread to be suspended Waiting for page_cleaner to finish flushing of buffer pool Pending checkpoint_writes: %lu. Pending log flush writes: %lu. Waiting for %lu 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! Background thread %s woke up during shutdown Waiting for archiver to finish archiving page and log Background thread %s woke up during shutdown Waiting for dirty buffer pages to be flushed Log 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 %llu Hex 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 %s 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 %s %s Redo 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 %s No 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 %s Apply batch completed! %s %s %s %s %s %s An 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 consistent Extending 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 %llu Database was not shutdown normally! Starting crash recovery. The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redo Cannot 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 database Redo 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 pool Recovery 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 %s Can't encrypt data of redo log %s %s Decryption 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 %s Old log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.com Semaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung. Waiting for %llu table(s) to be dropped Waiting for change buffer merge to complete number of bytes of change buffer just merged: %llu Can'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 - %s Encryption 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 %s Setting 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 %llu Renaming log file %s to %s New redo log files created, LSN=%llu Unable to open '%s' (error: %d). Cannot create construction log file '%s' for undo tablespace '%s'. Creating UNDO Tablespace %s Setting file %s size to %llu MB Physically writing the file full Error in creating %s: probably out of disk space Can't set encryption metadata for space %s Cannot read first page of '%s' - %s Undo tablespace number %lu was being truncated when mysqld quit. Cannot recover a truncated undo tablespace in read-only mode Reconstructing 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 %s Error creating file for %s Error reading encryption for %s Unable to open undo tablespace number %lu Opened %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 correctly Encryption 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 start Creating shared tablespace for temporary tables The %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 available PUNCH HOLE support not available 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. 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 %s 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. Compressed tables use zlib %s %s 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. %s Unable to create monitor file %s: %s Disabling background ibuf IO read threads. Cannot initialize AIO sub-system Initializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer pool Completed initialization of buffer pool Small 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 found The redo log file %s size %llu is not a multiple of innodb_page_size The 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 %s Tablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pages 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. Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pages 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. %s started; log sequence number %llu Waiting for purge to complete Waiting for dict_stats_thread to exit Query counter shows %lld queries still inside InnoDB at shutdown Shutdown completed; log sequence number %llu Cannot continue operation. %s %s %s %s %s %s %s %s %s Unable to read the existing undo truncate log file '%s'. The error is %s Undo tablespace %s is marked for truncate %s Truncating UNDO tablespace %s %s Cannot create truncate log for undo tablespace '%s'. %s Failed to truncate undo tablespace '%s'. %s Completed truncate of undo tablespace %s. %s %s %s %s %s %s %s %s %s %s %s %s %s %s Rollback of non-prepared transactions completed %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s Blocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back. %s gettimeofday() failed: %s Can't create UNDO tablespace %s %s %s 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. %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s Out of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity. %s 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. 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 %s Can'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 log Starting 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 %s Invalid redo log header checksum. Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9 %s 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 %s %s User 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 table The 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 %s Fatal error: %s Unexpected source's heartbeat data: %s The incident %s occurred on the source. Message: %s Source command %s failed: %s Relay log read failure: %s Relay log write failure: %s Replica failed to initialize connection metadata structure from the repository Replica failed to initialize applier metadata structure from the repository Got a packet bigger than 'max_allowed_packet' bytes Access to %.64s '%.64s.%.64s' is rejected. Unknown error Unknown 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 - %s Aborted 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 - %s Incorrect 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 - %s Incorrect 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 rules Cannot 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 %s Audit 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 operation No 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 completed Cannot boot server version %lu on data directory built by version %llu. Downgrade is not supported Received SHUTDOWN from user %s. Shutting down mysqld (Version: %s). The plugin encountered a critical error and will abort: %s Invalid 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. %s One 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 %s Source 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: %s Message 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: %s Error while executing a group configuration operation: %s Configuration operation '%s' terminated. %s Starting group operation local execution: %s Termination of group operation local execution: %s A 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: %s It 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 it Could 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 plugin The function '%s' failed. %s Do 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 session Unable to switch security context to user: %s Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT. Error in parsing %s '%s'.'%s' during upgrade. %s The 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': %s Error uninstalling plugin '%s': %s Partitioned 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 platform Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %s Could 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 ignored Failed 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: %zu Using undo tablespace '%s'. %s Unable to save the current state of tablespace '%s' to the data dictionary Cannot 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_ERROR SDI Compression failed, Z_MEM_ERROR SDI Compression failed, Z_STREAM_ERROR %s Expected 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_file ib_undo_trunc_before_dd_update ib_undo_trunc_before_done_logging ib_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. %s Clone 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: %d Can'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. %s Special handling for group search, {GA} not found User group retrieval: User object has group information Group 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 information Reserved port for ldaps using ldaps Get user proxy Get user proxy: User doesn't belongs to any group, user name will be treated as authenticated user. Get user proxy: configured mapping info: %s Get user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user. Process group proxy mapping Check delimiter after quote Processing delimiter Processing delimiter, separator = not found, resetting position "Processing delimiter, failed to get data for = separator try for separator ,." Processing delimiter, separator , not found, resetting position Processing delimiter: No mapping separator is found, end of group information Getting next mapping information Parsing mapping, current state: %d delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %s Mapping parsing error Trimming left spaces Checking if current characters is quote Not 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 instead Cannot 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 version Started auto-rejoin procedure attempt %lu of %lu Timeout while waiting for a view change event during the auto-rejoin procedure Auto-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 logging 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. Cannot grant roles to an anonymous user. Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %s Network Namespaces is not supported on this platform Unknown network namespace '%s' Network namespace not allowed for wildcard interface address setns() failed with error '%s' Wildcard address value not allowed for multivalued bind address The 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: %s Truncated a user name for %s that was too long while reading the persisted variables file Truncated a host name for %s that was too long while reading the persisted variables file The 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 Plugin '%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 conversion 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' 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: %s Lock order dependencies file <%s> (%d:%d) - (%d:%d) : %s Lock order scanner: (%d:%d) - (%d:%d) : %s The 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 %s Clone removing all user data for provisioning: %s Non 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: %s There was an issue when cloning from another server: %s There was an issue when trying to evaluate the best distributed recovery strategy while joining.%s 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. The group replication plugin could not kill the plugin routine for %s. %s 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. 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: %s Due to some issue on the previous step distributed recovery is now executing: %s Due 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 server Unknown 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 type Invalid argument count audit_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: %s The 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 %s Unknown 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: %.512s Cannot 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.%.64s The 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 upgrade Updating partition file name '%s' to '%s' and all other partition files during downgrade Updating partition file name '%s' to '%s' for import Unable 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 messages Elected primary member %s: %s Schema 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 dictionary 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. %s Upgrade cannot proceed due to an existing prepared XA transaction. Could not allocate memory for key_info when migrating table %s.%s 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' Failed to delete 5.7 undo tablespace: %s during upgrade Empty doublewrite file: %s Using '%s' for doublewrite Error reading doublewrite buffer from the system tablespace Cannot 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=6 The doublewrite filename '%s' is incorrect. %s Doublewrite file create failed: %s DBLWRThread: pthread_setaffinity() failed! %s %s Doublewrite file read failed: %s Dump of the data file page: %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s %s Doublewrite load file %s size %lu is not a multiple of the configured page size %lu" Doublewrite file %s truncate failed Doublewrite file %s failed to writ zeros Doublewrite create file %s size %lu is not a multiple of the configured page size %lu" %s %s %s %s %s Could not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts. Failed to delete 5.7 stat tablespace: %s during upgrade Installing ndbinfo schema version %s Installed ndbinfo schema is current. Not upgrading. Failed to upgrade ndbinfo schema. %s InnoDB 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 %s 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. 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. %s Scanned 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=6 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. 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 shutdown Found an entry in the 'role_edges' table with empty authorization ID; Skipped Found an entry in the 'role_edges' table with unknown authorization ID '%s'; Skipped Found an entry in the 'default_roles' table with empty authorization ID; Skipped Found an entry in the 'default_roles' table with unknown authorization ID '%s'; Skipped Couldn'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 %s The 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: %s Injected debug failure point: %s Timeout 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 log Could 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. %s 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. 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: %s Log 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 channel 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. %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 MiB InnoDB: 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. %s Failed to auto-prune file '%s', Error (%d): %s File '%s' auto-pruned Received an error while processing components from manifest file: %s Received an error while unloading components read from manifest file: %s Manifest 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' bits Error 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 : %s 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. '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 %s User 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 AUTOMATIC The group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channel group_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 ignored 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. Invalid table definition for '%s.%s'. %s Cannot 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 complete Time taken to initialize rseg using %u thread: %u ms. DDL failed to create a thread to load an index, fall back to single thread Debug_check_no_latching failed, slot->type=%d 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. 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: %s Clone DDL APPLY: %s Clone DDL Invalidate : %s Encryption key is loaded for undo tablespace '%s'. Ignoring encryption INFO size in redo log: %zu, expected: %zu Option --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 service 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. 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: %s Authentication 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 MiB The 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 variables Could not find master key %s in keyring A new master key %s could not be generated Failed to encrypt %s using %s Failed to decrypt %s using %s Persisting 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: %s thread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0 %s %s 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. 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 %s Neither found %s subdirectory, nor %s* files in %s Cannot 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. %s Failed 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%s Setting session values for system variables only makes sense in a user session (failed to set '%.256s'). BuildID[sha1]=%s Failed 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. %s Recovery: Generating index information for INSTANT DDL Table in 8.0.29 format Failed to switch resource group. %s Failed 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 %s Cannot 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 %s Status code %u: Completed Status code %u: %u%% complete Status code %u: %s Invalid 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 group Found page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lu preader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zu bulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zu bulkflusher: 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: %s Bulk loader: %s The first file being loaded contained less lines than the ignore clause Bulk reader: %s Bulk reader failed to initialize libcurl Bulk reader got libcurl error: %s Bulk reader got error response from server: %ld Bulk reader got error in communication with source server, check the error log for additional details Missing 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=%s LOAD 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 %s Column name %s and internally generated INSTANT DROP column name %s is causing a conflict. Field number: %llu too large, Total fields in Record: %zu. %s 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' 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 inserts Transaction ID: %lu found for resurrecting updates Identified table ID: %lu to acquire lock Acquired lock on table ID: %lu, name: %s Records read: %lu - Pages read: %lu Total records resurrected: %lu - Total pages read: %lu - Total tables acquired: %lu Resurrected %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 sandboxing Execution of alter table %s %s failed because %s. TP conn (port: managed(delta), active, opened, closed, added, dropped): %s Scheduled run of task %s failed Invalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %d Could 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: %s Heap 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 DIRECTORY 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. The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.
Simpan