⚝
One Hat Cyber Team
⚝
Your IP:
216.73.216.124
Server IP:
50.28.103.30
Server:
Linux host.jcukjv-lwsites.com 4.18.0-553.22.1.el8_10.x86_64 #1 SMP Tue Sep 24 05:16:59 EDT 2024 x86_64
Server Software:
nginx/1.28.0
PHP Version:
8.3.12
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
www
/
server
/
mysql
/
share
/
swedish
/
View File Name :
errmsg.sys
�� �* h H w � � K � � � = u � � � 4 c � � , c � � 6 K v � � � M | � � A � � C m � � C _ o � � � � " D d � � � A j � � � � , G � � " f � P g � � � � D � � . N � � ^ � � $ F \ � � = q � � c n � � � ( S � � � � I [ � S � @ u � � R { � I � / \ � � � ( � � & z � � o � � . } � � 5 _ � � � ! <! y! �! " 2" n" �" �" # �# �# �# $ �$ �$ �$ % 6% M% f% �% �% �% 6& Y& �& �& �& ' 1' �' �' �' 3( �( �( A) �) * g* �* �* + L+ }+ �+ , I, d, �, �, N- - �- �- . 3. k. �. �. �. / d/ �/ �/ 0 Y0 �0 �0 1 -1 `1 �1 �1 �1 ?2 `2 �2 �2 �2 3 M3 y3 �3 �3 �3 4 74 t4 �4 5 W5 p5 �5 �5 6 q6 �6 �6 �6 &7 t7 �7 �7 �7 38 b8 �8 �8 9 m9 �9 *: �: ; O; < E< d< �< �< = '= �= �= > ;> �> �> ? E? �? �? 1@ P@ y@ �@ �@ �@ =A iA �A �A �A �A �A B &B AB hB �B �B �B RC �C �C 'D ?D ^D D �D �D �D �D E E =E qE �E �E �E �E �E F 0F vF �F �F �F G QG �G �G H LH hH �H �H �H I GI �I �I J �J �J K %K <K kK �K �K �K �K 7L gL �L �L M *M `M �M �M �M �M N 1N PN {N �N �N �N *O WO �O �O �O �O 1P WP qP �P Q 3Q RQ iQ �Q �Q 6R �R �R S QS �S �S �S T AT qT �T �T U nU �U �U �V bW �W oX �X �X /Y hY �Y �Y 7Z �Z �Z [ v[ �[ $\ b\ z\ ] ,] I] �] �] �] ]^ �^ S_ �_ �_ 5` �` �` a Ra �a �a �b �b =c �c �c $d Td �d �d e 9e fe �e �e �e �e f Wf �f �f �f \g �g �g Eh �h �h 7i mi �i �i 7j �j �j k [k �k �k (l tl �l �l ?m �m �m n �n �n �n Go vo �o p /p �p �p ,q �q �q r Pr �r �r �r 0s }s t Ft �t �t �t �t u Ou cu uu �u �u Pv dv �v �v Lw kw �w �w �w �w x Ex �x �x �x y Ry ~y �y �y �y !z vz �z �z H{ �{ 5| �| �| } E} v} �} �} �} 4~ �~ �~ �~ ( E y � � F� k� �� Ѐ l� �� � )� h� �� ǂ D� ȃ �� +� �� �� �� ʄ ބ �� $� S� �� Ʌ �� 6� u� �� ܆ � 8� �� �� � � O� �� È � � 5� X� �� ɉ 7� ^� ˊ � ;� o� �� Ջ B� J� Q� [� h� r� ~� �� ܌ �� � I� r� �� ȍ � (� O� u� �� � ;� d� �� Ə � � R� �� � � �� R� �� �� T� Д \� ٕ ^� � �� �� `� Ƙ K� \� �� � .� X� �� ˚ � L� �� � %� X� �� �� � 6� �� � #� G� �� �� � S� �� ן q� � �� � Y� �� ע � @� V� r� C� (� � Ŧ �� O� �� � #� !� w� �� ݫ @� x� �� #� ]� �� � J� l� �� � �� ȯ � #� n� �� V� �� ̱ � 1� p� �� � 8� �� y� |� �� ̴ � (� �� "� �� �� � X� Ǹ � O� �� � 0� M� t� � m� ̻ ;� r� ټ )� v� н � � '� G� 5� j� �� � F� �� D� �� �� �� 8� �� �� �� t� �� Y� �� �� 1� F� k� �� �� �� �� � *� m� � �� �� =� �� � I� r� �� � �� �� 7� �� � [� �� � @� Z� <� {� �� � r� �� �� w� �� �� �� /� b� �� �� � V� �� �� �� � �� �� h� �� � 4� �� �� ,� �� �� � ~� �� � i� �� � �� � 9� �� �� %� {� �� J� �� � v� �� � @� �� 0� `� �� � N� �� � E� �� �� � U� � �� � L� _� ~� �� �� �� �� � � x� �� 1� n� �� �� 9� {� �� �� �� %� l� �� � \� �� �� �� � 2� ^� �� �� �� �� &� Q� }� �� � �� �� � 4� T� � �� =� �� � )� W� �� � � p� �� � %� �� � -� f� � ;� x� �� *� p� D� � *� x� � 0 � � � ` � � ' i � F � � 8 u � � � Q � ^ � � � � : Y � � & � � + � � � � � � Q ~ � ] � � a � � T � � V � � w � � � @ s � � � > � " g � � � H y � � / � � � K x � X � z v � / A h � � � ! ! �! +" �" �" # 8# b# x# �# �# �# )$ ,$ I$ _$ �$ �$ �$ % �% S& �& �& ,' �' Y( �( �( 7) �) �* hashchk isamchk NO YES Kan inte skapa filen '%-.200s' (Felkod: %d - %s) Kan inte skapa tabellen '%-.200s' (Felkod: %d) Kan inte skapa databasen '%-.192s' (Felkod: %d) Databasen '%-.192s' existerar redan Kan inte radera databasen '%-.192s'; databasen finns inte Fel vid radering av databasen (Kan inte radera '%-.192s'. Felkod: %d) Fel vid radering av databasen (Kan inte radera biblioteket '%-.192s'. Felkod: %d) Kan inte radera filen '%-.192s' (Felkod: %d - %s) Hittar inte posten i systemregistret Kan inte läsa filinformationen (stat) från '%-.200s' (Felkod: %d - %s) Kan inte inte läsa aktivt bibliotek. (Felkod: %d - %s) Kan inte låsa filen. (Felkod: %d - %s) Kan inte använda '%-.200s' (Felkod: %d - %s) Hittar inte filen '%-.200s' (Felkod: %d - %s) Kan inte läsa från bibliotek '%-.192s' (Felkod: %d - %s) Kan inte byta till '%-.192s' (Felkod: %d - %s) Posten har förändrats sedan den lästes i register '%-.192s' Disken är full (%s). Väntar tills det finns ledigt utrymme... (Felkod: %d - %s) Kan inte skriva, dubbel söknyckel i register '%-.192s' Fick fel vid stängning av '%-.192s' (Felkod: %d - %s) Fick fel vid läsning av '%-.200s' (Felkod %d - %s) Kan inte byta namn från '%-.210s' till '%-.210s' (Felkod: %d - %s) Fick fel vid skrivning till '%-.200s' (Felkod %d - %s) '%-.192s' är låst mot användning Sorteringen avbruten Formulär '%-.192s' finns inte i '%-.192s' Fick felkod %d från databashanteraren Tabellhanteraren for tabell '%-.192s' stödjer ej detta Hittar inte posten '%-.192s' Felaktig fil: '%-.200s' Fatalt fel vid hantering av register '%-.200s'; kör en reparation Gammal nyckelfil '%-.192s'; reparera registret '%-.192s' är skyddad mot förändring Oväntat slut på minnet, starta om programmet och försök på nytt (Behövde %d bytes) Sorteringsbufferten räcker inte till. Kontrollera startparametrarna Oväntat filslut vid läsning från '%-.192s' (Felkod: %d - %s) För många anslutningar Fick slut på minnet. Kontrollera om mysqld eller någon annan process använder allt tillgängligt minne. Om inte, försök använda 'ulimit' eller allokera mera swap Kan inte hitta 'hostname' för din adress Fel vid initiering av kommunikationen med klienten Användare '%-.48s'@'%-.64s' är ej berättigad att använda databasen %-.192s Användare '%-.48s'@'%-.64s' är ej berättigad att logga in (Använder lösen: %s) Ingen databas i användning Okänt kommando Kolumn '%-.192s' får inte vara NULL Okänd databas: '%-.192s' Tabellen '%-.192s' finns redan Okänd tabell '%-.100s' Kolumn '%-.192s' i %-.192s är inte unik Servern går nu ned Okänd kolumn '%-.192s' i %-.192s '%-.192s' finns inte i GROUP BY Kan inte använda GROUP BY med '%-.192s' Kommandot har både sum functions och enkla funktioner Antalet kolumner motsvarar inte antalet värden Kolumnnamn '%-.100s' är för långt Kolumnnamn '%-.192s finns flera gånger Nyckelnamn '%-.192s' finns flera gånger Dublett '%-.192s' för nyckel %d Felaktigt kolumntyp för kolumn '%-.192s' %s nära '%-.80s' på rad %d Frågan var tom Icke unikt tabell/alias: '%-.192s' Ogiltigt DEFAULT värde för '%-.192s' Flera PRIMARY KEY använda För många nycklar använda. Man får ha högst %d nycklar För många nyckeldelar använda. Man får ha högst %d nyckeldelar För lång nyckel. Högsta tillåtna nyckellängd är %d Nyckelkolumn '%-.192s' finns inte En BLOB '%-.192s' kan inte vara nyckel med den använda tabelltypen För stor kolumnlängd angiven för '%-.192s' (max= %lu). Använd en BLOB instället Det får finnas endast ett AUTO_INCREMENT-fält och detta måste vara en nyckel %s: klar att ta emot klienter Version: '%s' socket: '%s' port: %d" %s: Normal avslutning %s: Fick signal %d. Avslutar! %s: Avslutning klar %s: Stänger av tråd %ld; användare: '%-.48s' Kan inte skapa IP-socket Tabellen '%-.192s' har inget index som motsvarar det angivna i CREATE INDEX. Skapa om tabellen Fältseparatorerna är vad som förväntades. Kontrollera mot manualen Man kan inte använda fast radlängd med blobs. Använd 'fields terminated by' Textfilen '%-.128s' måste finnas i databasbiblioteket eller vara läsbar för alla Filen '%-.200s' existerar redan Rader: %ld Bortagna: %ld Dubletter: %ld Varningar: %ld Rader: %ld Dubletter: %ld Felaktig delnyckel. Nyckeldelen är inte en sträng eller den angivna längden är längre än kolumnlängden Man kan inte radera alla fält med ALTER TABLE. Använd DROP TABLE istället Kan inte ta bort '%-.192s'. Kontrollera att fältet/nyckel finns Rader: %ld Dubletter: %ld Varningar: %ld INSERT-table '%-.192s' får inte finnas i FROM tabell-listan Finns ingen tråd med id %lu Du är inte ägare till tråd %lu Inga tabeller angivna För många alternativ till kolumn %-.192s för SET Kan inte generera ett unikt filnamn %-.200s.(1-999) Tabell '%-.192s' kan inte uppdateras emedan den är låst för läsning Tabell '%-.192s' är inte låst med LOCK TABLES BLOB fält '%-.192s' kan inte ha ett DEFAULT-värde Felaktigt databasnamn '%-.100s' Felaktigt tabellnamn '%-.100s' Den angivna frågan skulle läsa mer än MAX_JOIN_SIZE rader. Kontrollera din WHERE och använd SET SQL_BIG_SELECTS=1 eller SET MAX_JOIN_SIZE=# ifall du vill hantera stora joins Okänt fel Okänd procedur: %-.192s Felaktigt antal parametrar till procedur %-.192s Felaktiga parametrar till procedur %-.192s Okänd tabell '%-.192s' i '%-.32s' Fält '%-.192s' är redan använt Felaktig användning av SQL grupp function Tabell '%-.192s' har en extension som inte finns i denna version av MySQL Tabeller måste ha minst 1 kolumn Tabellen '%-.192s' är full Okänd teckenuppsättning: '%-.64s' För många tabeller. MySQL can ha högst %d tabeller i en och samma join För många fält För stor total radlängd. Den högst tillåtna radlängden, förutom BLOBs, är %ld. Ändra några av dina fält till BLOB Trådstacken tog slut: Har använt %ld av %ld bytes. Använd 'mysqld --thread_stack=#' ifall du behöver en större stack Felaktigt referens i OUTER JOIN. Kontrollera ON-uttrycket Tabell hanteraren kan inte indexera NULL kolumner för den givna index typen. Ändra '%-.192s' till NOT NULL eller använd en annan hanterare Kan inte ladda funktionen '%-.192s' Kan inte initialisera funktionen '%-.192s'; '%-.80s' Man får inte ange sökväg för dynamiska bibliotek Funktionen '%-.192s' finns redan Kan inte öppna det dynamiska biblioteket '%-.192s' (Felkod: %d %-.128s) Hittar inte funktionen '%-.128s' in det dynamiska biblioteket Funktionen '%-.192s' är inte definierad Denna dator, '%-.64s', är blockerad pga många felaktig paket. Gör 'mysqladmin flush-hosts' för att ta bort alla blockeringarna Denna dator, '%-.64s', har inte privileger att använda denna MySQL server Du använder MySQL som en anonym användare och som sådan får du inte ändra ditt lösenord För att ändra lösenord för andra måste du ha rättigheter att uppdatera mysql-databasen Hittade inte användaren i 'user'-tabellen Rader: %ld Uppdaterade: %ld Varningar: %ld Kan inte skapa en ny tråd (errno %d) Antalet kolumner motsvarar inte antalet värden på rad: %ld Kunde inte stänga och öppna tabell '%-.192s Felaktig använding av NULL Fick fel '%-.64s' från REGEXP Man får ha både GROUP-kolumner (MIN(),MAX(),COUNT()...) och fält i en fråga om man inte har en GROUP BY-del Det finns inget privilegium definierat för användare '%-.48s' på '%-.64s' %-.128s ej tillåtet för '%-.48s'@'%-.64s' för tabell '%-.64s' %-.16s ej tillåtet för '%-.48s'@'%-.64s' för kolumn '%-.192s' i tabell '%-.192s' Felaktigt GRANT-privilegium använt Felaktigt maskinnamn eller användarnamn använt med GRANT Det finns ingen tabell som heter '%-.192s.%-.192s' Det finns inget privilegium definierat för användare '%-.48s' på '%-.64s' för tabell '%-.192s' Du kan inte använda detta kommando med denna MySQL version Du har något fel i din syntax Delayed insert thread couldn't get requested lock for table %-.192s Too many delayed threads in use Avbröt länken för tråd %ld till db '%-.192s', användare '%-.48s' (%-.64s) Kommunkationspaketet är större än 'max_allowed_packet' Fick läsfel från klienten vid läsning från 'PIPE' Fick fatalt fel från 'fcntl()' Kommunikationspaketen kom i fel ordning Kunde inte packa up kommunikationspaketet Fick ett fel vid läsning från klienten Fick 'timeout' vid läsning från klienten Fick ett fel vid skrivning till klienten Fick 'timeout' vid skrivning till klienten Resultatsträngen är längre än max_allowed_packet Den använda tabelltypen kan inte hantera BLOB/TEXT-kolumner Den använda tabelltypen kan inte hantera AUTO_INCREMENT-kolumner INSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLES Felaktigt kolumnnamn '%-.100s' Den använda tabelltypen kan inte indexera kolumn '%-.192s' Tabellerna i MERGE-tabellen är inte identiskt definierade Kan inte skriva till tabell '%-.192s'; UNIQUE-test Du har inte angett någon nyckellängd för BLOB '%-.192s' Alla delar av en PRIMARY KEY måste vara NOT NULL; Om du vill ha en nyckel med NULL, använd UNIQUE istället Resultet bestod av mera än en rad Denna tabelltyp kräver en PRIMARY KEY Denna version av MySQL är inte kompilerad med RAID Du använder 'säker uppdateringsmod' och försökte uppdatera en tabell utan en WHERE-sats som använder sig av en nyckel. %s Nyckel '%-.192s' finns inte in tabell '%-.192s' Kan inte öppna tabellen Tabellhanteraren för denna tabell kan inte göra %s Du får inte utföra detta kommando i en transaktion Fick fel %d vid COMMIT Fick fel %d vid ROLLBACK Fick fel %d vid FLUSH_LOGS Fick fel %d vid CHECKPOINT Avbröt länken för tråd %u till db '%-.192s', användare '%-.48s', host '%-.64s' (%-.64s) Tabellhanteraren klarar inte en binär kopiering av tabellen Binlog closed, cannot RESET MASTER Failed rebuilding the index of dumped table '%-.192s' Fel från master: '%-.64s' Fick nätverksfel vid läsning från master Fick nätverksfel vid skrivning till master Hittar inte ett FULLTEXT-index i kolumnlistan Kan inte utföra kommandot emedan du har en låst tabell eller an aktiv transaktion Okänd systemvariabel: '%-.64s' Tabell '%-.192s' är trasig och bör repareras med REPAIR TABLE Tabell '%-.192s' är trasig och senast (automatiska?) reparation misslyckades Warning: Några icke transaktionella tabeller kunde inte återställas vid ROLLBACK Transaktionen krävde mera än 'max_binlog_cache_size' minne. Öka denna mysqld-variabel och försök på nytt Denna operation kan inte göras under replikering; Gör STOP SLAVE först Denna operation kan endast göras under replikering; Konfigurera slaven och gör START SLAVE Servern är inte konfigurerade som en replikationsslav. Ändra konfigurationsfilen eller gör CHANGE MASTER TO Kunde inte initialisera replikationsstrukturerna. See MySQL fel fil för mera information Kunde inte starta en tråd för replikering Användare '%-.64s' har redan 'max_user_connections' aktiva inloggningar Man kan endast använda konstantuttryck med SET Fick inte ett lås i tid ; Försök att starta om transaktionen Antal lås överskrider antalet reserverade lås Updateringslås kan inte göras när man använder READ UNCOMMITTED DROP DATABASE är inte tillåtet när man har ett globalt läslås CREATE DATABASE är inte tillåtet när man har ett globalt läslås Felaktiga argument till %s '%-.48s'@'%-.64s' har inte rättighet att skapa nya användare Felaktig tabelldefinition; alla tabeller i en MERGE-tabell måste vara i samma databas Fick 'DEADLOCK' vid låsförsök av block/rad. Försök att starta om transaktionen Tabelltypen har inte hantering av FULLTEXT-index Kan inte lägga till 'FOREIGN KEY constraint' FOREIGN KEY-konflikt: Kan inte skriva barn FOREIGN KEY-konflikt: Kan inte radera fader Fick fel vid anslutning till master: %-.128s Fick fel vid utförande av command på mastern: %-.128s Fick fel vid utförande av %s: %-.128s Felaktig använding av %s and %s SELECT-kommandona har olika antal kolumner Kan inte utföra kommandot emedan du har ett READ-lås Blandning av transaktionella och icke-transaktionella tabeller är inaktiverat Option '%s' användes två gånger Användare '%-.64s' har överskridit '%s' (nuvarande värde: %ld) Du har inte privlegiet '%-.128s' som behövs för denna operation Variabel '%-.64s' är en SESSION variabel och kan inte ändrad med SET GLOBAL Variabel '%-.64s' är en GLOBAL variabel och bör sättas med SET GLOBAL Variabel '%-.64s' har inte ett DEFAULT-värde Variabel '%-.64s' kan inte sättas till '%-.200s' Fel typ av argument till variabel '%-.64s' Variabeln '%-.64s' kan endast sättas, inte läsas Fel använding/placering av '%s' Denna version av MySQL kan ännu inte utföra '%s' Fick fatalt fel %d: '%-.512s' från master vid läsning av binärloggen Slav SQL tråden ignorerade frågan pga en replicate-*-table regel Variabel '%-.192s' är av typ %s Felaktig FOREIGN KEY-definition för '%-.192s': %s Nyckelreferensen och tabellreferensen stämmer inte överens Operand should contain %d column(s) Subquery returnerade mer än 1 rad Okänd PREPARED STATEMENT id (%.*s) var given till %s Hjälpdatabasen finns inte eller är skadad Cyklisk referens i subqueries Konvertar kolumn '%s' från %s till %s Referens '%-.64s' stöds inte (%s) Varje 'derived table' måste ha sitt eget alias Select %u reducerades vid optimiering Tabell '%-.192s' från en SELECT kan inte användas i %-.32s Klienten stöder inte autentiseringsprotokollet som begärts av servern; överväg uppgradering av klientprogrammet. Alla delar av en SPATIAL index måste vara NOT NULL COLLATION '%s' är inte tillåtet för CHARACTER SET '%s' Slaven har redan startat Slaven har redan stoppat Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted) ZLIB: Not enough memory ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted) ZLIB: Input data corrupted Row %u was cut by GROUP_CONCAT() Row %ld doesn't contain data for all columns Row %ld was truncated; it contained more data than there were input columns 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 Använder handler %s för tabell '%s' Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s' Cannot drop one or more of the requested 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 MASTER are ignored because this MySQL slave was compiled without SSL support; they can be used later if MySQL slave 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 SLAVE UNTIL It is recommended to use --skip-slave-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave's mysqld restart SQL thread is not to be started so UNTIL options are ignored Felaktigt index namn '%-.100s' Felaktigt katalog namn '%-.100s' Storleken av 'Query cache' kunde inte sättas till %lu, ny storlek är %lu Kolumn '%-.192s' kan inte vara del av ett FULLTEXT index Okänd nyckel 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 Tabell %-.100s använd med '%s' är inte uppdateringsbar '%s' är inte aktiverad; För att aktivera detta måste du bygga om MySQL med '%s' definierad MySQL är startad med %s. Pga av detta kan du inte använda detta kommando Column '%-.100s' has duplicated value '%-.64s' in %s Truncated incorrect %-.32s 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' View's SELECT and view's field 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 '%-.64s' 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'. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger. '%-.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 table mysql.proc is 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' Syntaxfel: %-.64s PARTITIONering kräver definition av VALUES %-.64s för varje partition Endast %-.64s partitionering kan använda VALUES %-.64s i definition av partitionen MAXVALUE kan bara användas i definitionen av den sista partitionen Subpartitioner kan bara vara hash och key partitioner Subpartitioner måste definieras på alla partitioner om på en Antal partitioner definierade och antal partitioner är inte lika Antal subpartitioner definierade och antal subpartitioner är inte lika Konstanta uttryck eller slumpmässiga uttryck är inte tillåtna (sub)partitioneringsfunktioner Uttryck i RANGE/LIST VALUES måste vara ett konstant uttryck Fält i listan av fält för partitionering med key inte funnen i tabellen En lista av fält är endast tillåtet för KEY partitioner Partitioneringsinformationen i frm-filen är inte konsistent med vad som kan skrivas i frm-filen %-.192s-funktionen returnerar felaktig typ För %-.64s partitionering så måste varje partition definieras Värden i VALUES LESS THAN måste vara strikt växande för varje partition Värden i VALUES måste vara av samma typ som partitioneringsfunktionen Multipel definition av samma konstant i list partitionering Partitioneringssyntax kan inte användas på egen hand i en SQL-fråga Denna mix av lagringsmotorer är inte tillåten i denna version av MySQL För partitioneringsmotorn så är det nödvändigt att definiera alla %-.64s För många partitioner (inkluderande subpartitioner) definierades Det är endast möjligt att blanda RANGE/LIST partitionering med HASH/KEY partitionering för subpartitionering Misslyckades med att skapa specifik fil i lagringsmotor Ett BLOB-fält är inte tillåtet i partitioneringsfunktioner A %-.192s must include all columns in the table's partitioning function Antal %-.64s = 0 är inte ett tillåten värde Partitioneringskommando på en opartitionerad tabell är inte möjligt Foreign keys är inte ännu implementerad i kombination med partitionering Fel i listan av partitioner att %-.64s Det är inte tillåtet att ta bort alla partitioner, använd DROP TABLE istället COALESCE PARTITION kan bara användas på HASH/KEY partitioner REORGANIZE PARTITION kan bara användas för att omorganisera partitioner, inte för att ändra deras antal REORGANIZE PARTITION utan parametrar kan bara användas på auto-partitionerade tabeller som använder HASH partitionering %-.64s PARTITION kan bara användas på RANGE/LIST-partitioner ADD PARTITION med fel antal subpartitioner Åtminstone en partition måste läggas till vid ADD PARTITION Åtminstone en partition måste slås ihop vid COALESCE PARTITION Fler partitioner att reorganisera än det finns partitioner Duplicerat partitionsnamn %-.192s Det är inte tillåtet att stänga av binlog på detta kommando När ett antal partitioner omorganiseras måste de vara i konsekutiv ordning Reorganisering av rangepartitioner kan inte ändra den totala intervallet utom för den sista partitionen där intervallet kan utökas Partition function not supported in this version for this handler Partition state kan inte definieras från CREATE/ALTER TABLE %-.64s stödjer endast 32 bitar i integers i 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 master and slave does not match: %s Slave running with --log-slave-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 Column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error. 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 Partitionskonstanten är utanför partitioneringsfunktionens domän Denna partitioneringsfunktion är inte tillåten Error in DDL log Det är inte tillåtet att använda NULL-värden i VALUES LESS THAN Felaktigt partitionsnamn 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 inte användas i en partitionerad tabell Cannot activate '%-.64s' log The server was not built with row-based replication Avkodning av base64 sträng misslyckades 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 Dublett '%-.64s' för nyckel '%-.192s' 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 occured on the master. Message: %s Table has no partition for some existing values Detta är inte säkert att logga i statement-format, för BINLOG_FORMAT = STATEMENT. %s Fatal error: %s Relay log read failure: %s Relay log write failure: %s Failed to create %s Master 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 slave 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 master info 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 master'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 Databas Tabell Partition Subpartition Temporär Namnändrad 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 slave 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 slaves. 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 slave. Statement is unsafe because it uses a system variable that may have a different value on the slave. Statement is unsafe because it uses a system function that may return a different value on the slave. 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 Misslyckades läsa från .par filen Värden i VALUES för partition '%-.64s' måste ha typen INT Användare '%-.48s'@'%-.64s' är ej berättigad att logga in 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 `slave_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 master and the slave. 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 master and the slave. 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 master and the slave. 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 master and the slave. 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 master and the slave. 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 master and the slave. 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 master and the slave. 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 master and the slave. 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 master delay exceeds the maximum %u Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided) Attributet '%-.64s' är olika mellan partition och tabell Tabellen att byta ut mot partition är partitionerad: '%-.64s' Tabellen att byta ut mot partition är temporär: '%-.64s' Subpartitionerad tabell, använd subpartition istället för partition Okänd partition '%-.64s' i tabell '%-.64s' Tabellerna har olika definitioner Hittade en rad som inte passar i partitionen 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' Tabellen att byta ut mot partition har foreign key referenser: '%-.64s' Key value '%-.192s' was not found in table '%-.192s.%-.192s' Data for column '%s' too 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 () klausul för en icke partitionerad tabell Hittade en rad som inte passar i någon given partition Det finns ingen partition som heter '%-.64s' Failure while changing the type of replication repository: %s. The creation of some temporary tables could not be rolled back. Some temporary tables were dropped, but these operations could not be rolled back. %s is not supported in multi-threaded slave 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 stöds ej för partitionerade tabeller. Invalid condition number Sending passwords in plain text without SSL/TLS is extremely insecure. Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information. FOREIGN KEY constraint för tabell '%.192s', posten '%-.192s' kan inte uppdatera barntabell '%.192s' på grund av nyckel '%.192s' FOREIGN KEY constraint för tabell '%.192s', posten '%-.192s' kan inte uppdatera en barntabell på grund av UNIQUE-test Setting authentication options is not possible when only the Slave 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 MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active. CHANGE MASTER TO MASTER_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-slave-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. The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. Replicate the missing transactions from elsewhere, or provision a new slave from backup. Consider increasing the master'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) Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. 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 MASTER cannot be executed when the slave was stopped with an error or killed in MTS mode. Consider using RESET SLAVE or START SLAVE UNTIL. Cannot recover after SLAVE 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 Slave 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 Supports only YEAR or YEAR(4) column. 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 constaint. Missing index for constraint '%s' in the foreign table '%s' Failed to add the foreign key constaint. 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. Check if the correct password algorithm is being used with the PASSWORD() function. 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_slave_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 Dublett för nyckel '%-.192s' Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'. cannot silently convert NULL values, as required in this SQL_MODE Your password has expired. To log in you must change it using a client that supports expired passwords. Hittade en rad i fel partition %s Cannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of slave_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' Slave failed to initialize master info structure from the repository Slave failed to initialize relay log info structure from the repository Access denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting. InnoDB is in read only mode. STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete. STOP SLAVE command execution is incomplete: Slave 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_forced_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'. Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been committed on master 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. 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. File %s is corrupted Query partially completed on the master (error on master: %d) and was aborted. There is a chance that your master is inconsistent at this point. If you are sure that your master is ok, run this query manually on the slave and then restart the slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;. Query:'%s' Query caused different errors on master and slave. Error on master: message (format)='%s' error code=%d; Error on slave: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 slave. Cannot DISCARD/IMPORT tablespace associated with temporary table Foreign key cascade delete/update exceeds max depth of %d. Column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error. 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 slave sql thread; run STOP SLAVE 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 slave io thread; run STOP SLAVE IO_THREAD FOR CHANNEL '%s' first. This operation may not be safe when the slave 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 slave_open_temp_tables = 0. CHANGE MASTER TO with a MASTER_LOG_FILE clause but no MASTER_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 Expression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated query Slave worker has stopped after at least one previous worker encountered an error when slave-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the slave after fixing any failed threads, you should fix this worker as well. slave_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 occured 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 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'. 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 replication slave 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 Slave channel '%s' does not exist. A slave 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 slave info objects for channel '%s'. Multiple channels exist on the slave. 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 SLAVE FOR CHANNEL '%s' first This operation requires running replication threads; configure slave and run START SLAVE 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 slave sql thread; run STOP SLAVE SQL_THREAD FOR CHANNEL '%s' first. When sql_slave_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START SLAVE [SQL_THREAD]'. Value of sql_slave_skip_counter can only be used by one SQL thread at a time. Please use 'START SLAVE [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_slave_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. 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' cannot be used in key specification. 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). User %s does not exist. User %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 neccessary 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 plugin 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 plugin 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 run mysql_upgrade. RESET MASTER 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 slaves 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_ACL needed to perform operation SUPER privilege 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 replication slave. 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