"Dan Houtz" <[EMAIL PROTECTED]> wrote: > I'm currently trying to setup replication following the directions from the mysql > manual, however, once I configure the slave server with the server-id parameter, it > fails to load. If I remove server-id=2 from my.cnf then the server starts up fine. > I'm hoping someone can help me out: > > Master and Slace are both running mySQL 3.23.52 > > Master Config: > > [mysqld] > datadir=/var/lib/mysql > socket=/var/lib/mysql/mysql.sock > skip-innodb > log-bin > server-id=1 > > [mysql.server] > user=mysql > basedir=/var/lib > > [safe_mysqld] > err-log=/var/log/mysqld.log > Pid-file=/var/run/mysqld/mysqld.pid > > Slave Config: > > [mysqld] > datadir=/var/lib/mysql > socket=/var/lib/mysql/mysql.sock > master-host=192.168.0.8 > master-user=replicate > master-password=password > server-id=2 > > [mysql.server] > user=mysql > basedir=/var/lib > > [safe_mysqld] > err-log=/var/log/mysqld.log > pid-file=/var/run/mysqld/mysqld.pid > > > here is what the slave server logs when started (it appears to hang on each > attempted start/-restart): > > > Number of processes running now: 1 > mysqld process hanging, pid 22725 - killed > 030604 15:44:44 mysqld restarted > Cannot initialize InnoDB as 'innodb_data_file_path' is not set. > If you do not want to use transactional InnoDB tables, add a line > skip-innodb > to the [mysqld] section of init parameters in your my.cnf > or my.ini. If you want to use InnoDB tables, add to the [mysqld] > section, for example, > innodb_data_file_path = ibdata1:10M:autoextend > But to get good performance you should adjust for your hardware > the InnoDB startup options listed in section 2 at > http://www.innodb.com/ibman.html > /usr/libexec/mysqld: ready for connections > > Number of processes running now: 1 > mysqld process hanging, pid 22749 - killed > 030604 15:44:44 mysqld restarted > 030604 15:44:44 Can't start server: Bind on TCP/IP port: Address already in > use > 030604 15:44:44 Do you already have another mysqld server running on port: > 3306 ? > 030604 15:44:44 Aborting > > 030604 15:44:44 /usr/libexec/mysqld: Shutdown Complete > > 030604 15:44:44 mysqld ended >
But it's not a replication related error. Do you use InnoDB? Do you have any entries in the my.cnf related to the InnoDB startup options? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
