> > - make sure log-bin is enabled on both master and slave > (looks like it is not present in the slave config) > > Why is log-bin needed on the slave? I thought the master logs changes > and the slave reads those changes and updates it's copy. Why should > the slave also log changes it is making? There was no mention of this > in the docs.
You are right, log-bin is not required on a slave. I have it in my setup with log-slave-updates on for a chained replication where slave works as master as well. > > - check replication account permissions on the master. I > don't remember details, but you can find required permissions > in the docs on mysql web site, or doc file in mysql > installation directory. > > Turns out when my hosting provider "installed" MySQL 4.1, it was > actually an install over a 3.x data directory. The Priv tables were > never updated, so I never had the appropriate "REPLICATION SLAVE" > Priv, so the thread never started. It never did say why it did not > start though. Check this one out http://dev.mysql.com/doc/mysql/en/Upgrading-grant-tables.html for priv table upgrade. Also you slave account may need more permissions if you want to use LOAD * FROM MASTER commands. > Threads are now running, but data is not getting replicated. Need to > figure that out now. Below are settings I have for both slave and master. Maybe you can try them in your setup. default-character-set=utf8 # time zone has to be the same on master and slave for correct replication (from 4.1) default-time-zone=GMT log_warnings log_slow_queries log-bin log-slave-updates slave_compressed_protocol=1 # skip illegal collation error slave-skip-errors=1267 > thanks again. > Frank > Attention: Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material from any system and destroy any copies. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
