When setting up replication, MySQL may occasionally throw this error:
ERROR 1200 (HY000): The server is not configured as a slave; fix in config file or with CHANGE MASTER TO”
The troubleshooting steps are simple and usually are the result of a common configuration oversight.
- Ensure you have the server_id value configured in the my.cnf
- Ensure you have actually executed the appropriate CHANGE MASTER TO statement.
- Ensure the server_id value is unique per-server. The best way to do this is by using the ‘long’ value of the server’s IP address. You can get this easily with PHP’s “ip2long()” function.
That’s all there is to it!
The solution is as follows:
- Log into MySQL
- Change to the database where the table resides
- Execute the following:
ALTER TABLE [TableName] ENGINE=InnoDB;
Your MyISAM issues are now history.
Sometimes, you need to do a full dump of your databases to import to another server.
Continue reading MySQL/General – Dump all databases
Occasionally, when working in directories with large numbers of files and/or directories contained within them, you will get an error stating: Too many arguments.
This is not an error from the application. Rather, it is an error from the shell erroring on ARG_MAX limit reached.
Continue reading Linux/General – tar – Too many arguments
A default install of MySQL has anonymous users and root users with access via ‘%’ (all outside hosts) and a generally useless ‘test’ database.
Continue reading MySQL/Security – Cleaning up post-install
Sometimes, you may like a bit of security-through-obscurity. Some PCI providers even require this.
Continue reading Apache/Security – Hide Apache Version Number
PCI compliance tests require you to disable weak ciphers and older TLS support.
Continue reading Apache/PCI – Disable Weak Cipher and older TLS Support
Some PCI tests require that you disable the Apache TRACE method as this can reveal sensitive information about the server.
Continue reading Apache/PCI – Disable TRACE Method