[EMAIL PROTECTED] wrote:

> What happens when you do a show slave status on the slave machine

This:

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 10 to server version: 4.0.15-log

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show slave status
    -> ;
+-------------+-------------+-------------+---------------+-----------------+---------------------+-----------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+------------+------------+--------------+---------------------+-----------------+
| Master_Host | Master_User | Master_Port | Connect_retry |
Master_Log_File | Read_Master_Log_Pos | Relay_Log_File        |
Relay_Log_Pos | Relay_Master_Log_File | Slave_IO_Running |
Slave_SQL_Running | Replicate_do_db | Replicate_ignore_db | Last_errno |
Last_error | Skip_counter | Exec_master_log_pos | Relay_log_space |
+-------------+-------------+-------------+---------------+-----------------+---------------------+-----------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+------------+------------+--------------+---------------------+-----------------+
| 123.123.123.123 | rep1        | 3306        | 60           
|                 | 4                   | n1-relay-bin.001 |
4             |                       | No               |
Yes               |                 |                     | 0         
|            | 0            | 0                   | 4               |
+-------------+-------------+-------------+---------------+-----------------+---------------------+-----------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+------------+------------+--------------+---------------------+-----------------+
1 row in set (0.00 sec)

mysql> quit
Bye


> Can you ping the master from the slave?
yes

> What do you have in the master.info file
master.info

4
123.123.123.123
repl
repman
3306
60

One further point however makes me think that the origin of the 1236
error code probably lies elsewhere:

A colleague set up a test replication master/slave installation on a
couple of machines USING MY my.cnf for the master and slave respectively
and on his setup everything seemed to work - in any case there was no
error 1236.

My MySQL is 4.0.15-9, his is 4.0.17.
My Linux is SuSE 8.2, his is 7.3

Any further thoughts, we are snookered at the moment and haven't got
much of a notion what to do next (other than radical re-installations).

Regards, 

Mike Anderson

> 
> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> 
> On 2/5/04, 12:19:29 PM, <[EMAIL PROTECTED]> wrote regarding Re: replication: 
> slave returns a 1236 error_code.:

> 
> > Since you asked ......
> > here is the my.cnf from the slave:
> > I "Think" it is ok:
> 
> > In the .cnf file I have edited out the IP addresses and password for 
> obvious
> > reasons.
> 
> > ########################################################
> > # Example mysql config file for medium systems.
> >  #
> >  # This is for a system with little memory (32M - 64M) where MySQL plays
> >  # a important part and systems up to 128M very MySQL is used together 
> with
> >  # other programs (like a web server)
> >  #
> >  # You can copy this file to
> >  # /etc/my.cnf to set global options,
> >  # mysql-data-dir/my.cnf to set server-specific options (in this
> >  # installation this directory is /var/lib/mysql) or
> >  # ~/.my.cnf to set user-specific options.
> >  #
> >  # One can in this file use all long options that the program supports.
> >  # If you want to know which options a program support, run the program
> >  # with --help option.
> 
> >  # The following options will be passed to all MySQL clients
> >  [client]
> >  #password    = your_password
> >  port        = 3306
> >  socket        = /var/lib/mysql/mysql.sock
> 
> >  # Here follows entries for some specific programs
> 
> >  # The MySQL server
> >  [mysqld]
> >  port        = 3306
> >  socket        = /var/lib/mysql/mysql.sock
> >  skip-locking
> >  key_buffer = 16M
> >  max_allowed_packet = 1M
> >  table_cache = 64
> >  sort_buffer_size = 512K
> >  net_buffer_length = 8K
> >  myisam_sort_buffer_size = 8M
> 
> >  # Don't listen on a TCP/IP port at all. This can be a security 
> enhancement,
> 
> >  # if all processes that need to connect to mysqld run on the same host.
> >  # All interaction with mysqld must be made via Unix sockets or named 
> pipes.
> 
> >  # Note that using this option without enabling named pipes on Windows
> >  # (via the "enable-named-pipe" option) will render mysqld useless!
> >  #
> >  #skip-networking
> 
> >  # Replication Master Server (default)
> >  # binary logging is required for replication
> >  log-bin
> 
> >  # required unique id between 1 and 2^32 - 1
> >  # defaults to 1 if master-host is not set
> >  # but will not function as a master if omitted
> >  server-id=2
> 
> >  # Replication Slave (comment out master section to use this)
> >  #
> >  # To configure this host as a replication slave, you can choose between
> >  # two methods :
> >  #
> >  # 1) Use the CHANGE MASTER TO command (fully described in our manual) -
> >  #    the syntax is:
> >  #
> >  #    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
> >  #    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
> >  #
> >  #    where you replace <host>, <user>, <password> by quoted strings and
> >  #    <port> by the master's port number (3306 by default).
> >  #
> >  #    Example:
> >  #
> >  #CHANGE MASTER TO MASTER_HOST='nimbus2.hexal.de', MASTER_PORT=3306,
> >  #MASTER_USER='rep1', MASTER_PASSWORD='repman';
> >  #
> >  # OR
> >  #
> >  # 2) Set the variables below. However, in case you choose this method, 
> then
> 
> >  #    start replication for the first time (even unsuccessfully, for 
> example
> 
> >  #    if you mistyped the password in master-password and the slave fails 
> to
> 
> >  #    connect), the slave will create a master.info file, and any later
> >  #    change in this file to the variables' values below will be ignored 
> and
> 
> >  #    overridden by the content of the master.info file, unless you 
> shutdown
> 
> >  #    the slave server, delete master.info and restart the slaver server.
> >  #    For that reason, you may want to leave the lines below untouched
> >  #    (commented) and instead use CHANGE MASTER TO (see above)
> >  #
> >  # required unique id between 2 and 2^32 - 1
> >  # (and different from the master)
> >  # defaults to 2 if master-host is set
> >  # but will not function as a slave if omitted
> >  #server-id     = 2
> >  #
> >  # The replication master for this slave - required
> >  master-host=  123.123.123.123
> >  #
> >  # The username the slave will use for authentication when connecting
> >  # to the master - required
> >  master-user= rep1
> >  #
> >  # The password the slave will authenticate with when connecting to
> >  # the master - required
> >  master-password= <PASSWORD GOES HERE>
> >  #
> >  # The port the master is listening on.
> >  # optional - defaults to 3306
> >  #master-port     =  <port>
> >  #
> >  # binary logging - not required for slaves, but recommended
> >  log-bin
> 
> >  # Point the following paths to different dedicated disks
> >  tmpdir        = /tmp/
> >  #log-update     = /var/log/nim1rep
> >  log-update
> 
> >  # Uncomment the following if you are using BDB tables
> >  #bdb_cache_size = 4M
> >  #bdb_max_lock = 10000
> 
> >  # Uncomment the following if you are using InnoDB tables
> >  #innodb_data_home_dir = /var/lib/mysql/
> >  #innodb_data_file_path = ibdata1:10M:autoextend
> >  #innodb_log_group_home_dir = /var/lib/mysql/
> >  #innodb_log_arch_dir = /var/lib/mysql/
> >  # You can set .._buffer_pool_size up to 50 - 80 %
> >  # of RAM but beware of setting memory usage too high
> >  #innodb_buffer_pool_size = 16M
> >  #innodb_additional_mem_pool_size = 2M
> >  # Set .._log_file_size to 25 % of buffer pool size
> >  #innodb_log_file_size = 5M
> >  #innodb_log_buffer_size = 8M
> >  #innodb_flush_log_at_trx_commit = 1
> >  #innodb_lock_wait_timeout = 50
> 
> >  # The safe_mysqld script
> >  [safe_mysqld]
> >  err-log=/var/lib/mysql/mysqld.log
> 
> >  [mysqldump]
> >  quick
> >  max_allowed_packet = 16M
> 
> >  [mysql]
> >  no-auto-rehash
> >  # Remove the next comment character if you are not familiar with SQL
> >  #safe-updates
> 
> >  [isamchk]
> >  key_buffer = 20M
> >  sort_buffer_size = 20M
> >  read_buffer = 2M
> >  write_buffer = 2M
> 
> >  [myisamchk]
> >  key_buffer = 20M
> >  sort_buffer_size = 20M
> >  read_buffer = 2M
> >  write_buffer = 2M
> 
> >  [mysqlhotcopy]
> >  interactive-timeout
> 
> 
> > > Is the server Id for your slave setup? What does the my.cnf for the slav
> > > e
> > > look like?
> > >
> > > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> > >
> > > On 2/5/04, 10:17:11 AM, <[EMAIL PROTECTED]> wrote regarding replication:
> > > slave returns a 1236 error_code.:
> > >
> > >
> > > > Hallo,
> > >
> > > > I am having trouble setting up replication. After sorting out most
> > > > things I get a connection from the slave to the master, but then a
> > > > mysql_errorno=1236. Here is an extract of the system log:
> > >
> > > > ######################################################################
> > > ##
> > > > ###################
> > > > 040205 16:45:42  mysqld started
> > > > /usr/sbin/mysqld: ready for connections.
> > > > Version: '4.0.15-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306
> > >
> > > > 040205 16:45:42  Slave I/O thread: connected to master
> > > > '[EMAIL PROTECTED]:3306',  replication started in log 'FIRST' at
> > > > position 4
> > > > 040205 16:45:42  Error reading packet from server: Misconfigured maste
> > > r
> > > > - server id was not set (server_errno=1236)
> > > > 040205 16:45:42  Got fatal error 1236: 'Misconfigured master - server
> > > id
> > > > was not set' from master when reading data from binary log
> > > > 040205 16:45:42  Slave I/O thread exiting, read up to log 'FIRST',
> > > > position 4
> > >
> > >
> > > > However, in the master, the serveri-id is already set to 1. (see below
> > > ).
> > > > In addition, the slave contains the correct
> > > > user parameters to login on the master. (The ip-address above is a fak
> > > e)
> > >
> > > > Here is aome of the my.cnf file from the master:
> > >
> > > > ######################################################################
> > > ##
> > > > ##################
> > > > # Example mysql config file for medium systems.
> > > > #
> > > > # This is for a system with little memory (32M - 64M) where MySQL play
> > > s
> > > > # a important part and systems up to 128M very MySQL is used together
> > > > with
> > > > # other programs (like a web server)
> > > > #
> > > > # You can copy this file to
> > > > # /etc/my.cnf to set global options,
> > > > # mysql-data-dir/my.cnf to set server-specific options (in this
> > > > # installation this directory is /var/lib/mysql) or
> > > > # ~/.my.cnf to set user-specific options.
> > > > #
> > > > # One can in this file use all long options that the program supports.
> > >
> > > > # If you want to know which options a program support, run the program
> > >
> > > > # with --help option.
> > >
> > > > # The following options will be passed to all MySQL clients
> > > > [client]
> > > > #password     = your_password
> > > > port          = 3306
> > > > socket                = /var/lib/mysql/mysql.sock
> > >
> > > > # Here follows entries for some specific programs
> > >
> > > > # The MySQL server
> > > > [mysqld]
> > > > port          = 3306
> > > > socket                = /var/lib/mysql/mysql.sock
> > > > skip-locking
> > > > key_buffer = 16M
> > > > max_allowed_packet = 1M
> > > > table_cache = 64
> > > > sort_buffer_size = 512K
> > > > net_buffer_length = 8K
> > > > myisam_sort_buffer_size = 8M
> > > > log-bin
> > > > log-bin-index
> > >
> > > > # Don't listen on a TCP/IP port at all. This can be a security
> > > > enhancement,
> > > > # if all processes that need to connect to mysqld run on the same host
> > > .
> > > > # All interaction with mysqld must be made via Unix sockets or named
> > > > pipes.
> > > > # Note that using this option without enabling named pipes on Windows
> > > > # (via the "enable-named-pipe" option) will render mysqld useless!
> > > > #
> > > > #skip-networking
> > >
> > > > # Replication Master Server (default)
> > > > # binary logging is required for replication
> > > > # log-bin
> > >
> > > > # required unique id between 1 and 2^32 - 1
> > > > # defaults to 1 if master-host is not set
> > > > # but will not function as a master if omitted
> > >
> > > > server-id=1
> > >
> > > > <snip>
> > >
> > >
> > > > Can anyone give me a pointer to what might be wrong ?? Whatever it is
> > > it
> > > > doesn't seem to really be a missing master server-id.
> > >
> > > > Thanks
> > >
> > > > Mike Anderson
> > >
> > >
> > > > --
> > > > I saw the best minds of my generation
> > > > destroyed by madness. Allen Ginsberg 1956.
> > >
> > >
> > > > --
> > > > MySQL General Mailing List
> > > > For list archives: http://lists.mysql.com/mysql
> > > > To unsubscribe:
> > > http://lists.mysql.com/[EMAIL PROTECTED]
> > >
> > > --
> > > MySQL General Mailing List
> > > For list archives: http://lists.mysql.com/mysql
> > > To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]
> > >
> 
> > --
> > I saw the best minds of my generation
> > destroyed by madness. Allen Ginsberg 1956.


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to