Error 1794: Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave

You are viewing an old version of this article. View the current version here.

Error Code	SQLSTATE	Error	Description
1794	HY000	ER_SLAVE_CONFIGURATION	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 MariaDB error log

Possible Causes and Solutions

Possible Causes and Solutions

This article doesn't currently contain any content. You can help!

Comments

Comments loading...

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.

↑ MariaDB Error Codes 1700 to 1799 ↑
Error 1700: GRANT with IDENTIFIED WITH is illegal because the user already exists
Error 1701: Cannot truncate a table referenced in a foreign key constraint
Error 1702: Plugin is force_plus_permanent and can not be unloaded
Error 1703: The requested value for the heartbeat period is less than 1 millisecond
Error 1704: The requested value for the heartbeat period exceeds the value of slave_net_timeout seconds
Error 1705: Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again
Error 1706: Primary key/partition key update is not allowed since the table is updated both as and
Error 1707: Table rebuild required. Please do "ALTER TABLE FORCE" or dump/reload to fix it!
Error 1708: The value of should be no less than the value of
Error 1709: Index column size too large. The maximum column size is bytes.
Error 1710: Trigger has an error in its body
Error 1711: Unknown trigger has an error in its body
Error 1712: Index is corrupted
Error 1713: Undo log record is too big
Error 1714: INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored
Error 1715: 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
Error 1716: REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced
Error 1717: CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored
Error 1718: CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced
Error 1719: UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored
Error 1720: You should never see it
Error 1721: You should never see it
Error 1722: Statements writing to a table with an auto-increment column after selecting from another table are unsafe
Error 1723: 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
Error 1724: INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe
Error 1725: Table is being used in foreign key check.
Error 1726: Storage engine does not support system tables
Error 1727: INSERT into autoincrement field which is not the first part in the composed primary key is unsafe
Error 1728: Cannot load from. The table is probably corrupted
Error 1729: The requested value for the master delay exceeds the maximum
Error 1730: Only Format_description_log_event and row events are allowed in BINLOG statements
Error 1731: Non matching attribute between partition and table
Error 1732: Table to exchange with partition is partitioned
Error 1733: Table to exchange with partition is temporary
Error 1734: Subpartitioned table, use subpartition instead of partition
Error 1735: Unknown partition in table
Error 1736: Tables have different definitions
Error 1737: Found a row that does not match the partition
Error 1738: Option binlog_cache_size is greater than max_binlog_cache_size; setting binlog_cache_size equal to max_binlog_cache_size.
Error 1739: Cannot use access on index due to type or collation conversion on field
Error 1740: Table to exchange with partition has foreign key references
Error 1741: Key value was not found in table
Error 1742: Data for column too long
Error 1743: Replication event checksum verification failed while reading from network.
Error 1744: Replication event checksum verification failed while reading from a log file
Error 1745: Option binlog_stmt_cache_size is greater than max_binlog_stmt_cache_size
Error 1746: Can't update table while is being created
Error 1747: PARTITION () clause on non partitioned table
Error 1748: Found a row not matching the given partition set
Error 1749: partition doesn't exist
Error 1750: Failure while changing the type of replication repository
Error 1751: The creation of some temporary tables could not be rolled back.
Error 1752: Some temporary tables were dropped, but these operations could not be rolled back.
Error 1753: is not supported in multi-threaded slave mode
Error 1754: The number of modified databases exceeds the maximum
Error 1755: Cannot execute the current event group in the parallel mode
Error 1756: %s
Error 1757: FULLTEXT index is not supported for partitioned tables
Error 1758: Invalid condition number
Error 1759: Sending passwords in plain text without SSL/TLS is extremely insecure
Error 1760: Storing MariaDB user name or password information in the master.info repository is not secure
Error 1761: Foreign key constraint for table, record would lead to a duplicate entry in table
Error 1762: Foreign key constraint for table, record would lead to a duplicate entry in a child table
Error 1763: Setting authentication options is not possible when only the Slave SQL Thread is being started
Error 1764: The table does not have FULLTEXT index to support this query
Error 1765: The system variable cannot be set in stored functions or triggers
Error 1766: The system variable cannot be set when there is an ongoing transaction
Error 1767: The system variable @@SESSION.GTID_NEXT has the value which is not listed in @@SESSION.GTID_NEXT_LIST
Error 1768: The system variable @@SESSION.GTID_NEXT cannot change inside a transaction
Error 1769: The statement 'SET' cannot invoke a stored function
Error 1770: The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL
Error 1771: Skipping transaction because it has already been executed and logged
Error 1772: Malformed GTID set specification
Error 1773: Malformed GTID set encoding
Error 1774: Malformed GTID specification
Error 1775: Impossible to generate Global Transaction Identifier: the integer component reached the maximal value
Error 1776: Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active
Error 1777: CHANGE MASTER TO MASTER_AUTO_POSITION = 1 can only be executed when @@GLOBAL.GTID_MODE = ON
Error 1778: Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT != AUTOMATIC
Error 1779: GTID_MODE = ON or GTID_MODE = UPGRADE_STEP_2 requires DISABLE_GTID_UNSAFE_STATEMENTS = 1
Error 1780: @@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_1 or UPGRADE_STEP_2 requires --log-bin and --log-slave-updates
Error 1781: @@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF
Error 1782: @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON
Error 1783: @@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF
Error 1784: Found a Gtid_log_event or Previous_gtids_log_event when @@GLOBAL.GTID_MODE = OFF
Error 1785: When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions
Error 1786: CREATE TABLE ... SELECT is forbidden when @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1
Error 1787: When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can be executed in a non-transactional context only
Error 1788: The value of @@GLOBAL.GTID_MODE can only change one step at a time
Error 1789: 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
Error 1790: @@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID
Error 1791: Unknown EXPLAIN format name
Error 1792: Cannot execute statement in a READ ONLY transaction
Error 1793: Comment for table partition is too long
Error 1794: Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave
Error 1795: InnoDB presently supports one FULLTEXT index creation at a time
Error 1796: Cannot create FULLTEXT index on temporary InnoDB table
Error 1797: Column is of wrong type for an InnoDB FULLTEXT index
Error 1798: Index '%s' is of wrong type for an InnoDB FULLTEXT index
Error 1799: Creating index required more than 'innodb_online_alter_log_max_size' bytes of modification log

Error 1794: Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave

Contents

Possible Causes and Solutions

Comments

Products

Services

Pricing

Resources

About Us

Download MariaDB