Now it's ok
I have just deleted all logs and relay files included master.info and 
relay-log.info.
The log files were named fep1_xxxxx, while the host is named differently ( 
\\arlati-e ).
Mybe the "relay-log=fep1-relay-bin" is not working well, so the replication 
looks only for files named arlati-e_xxxx despite the realay-log directive.


-----Messaggio originale-----
Da: Enzo Arlati 
Inviato: lunedì 23 ottobre 2006 16.04
A: [EMAIL PROTECTED] Mysql. Com (E-mail)
Oggetto: replica on 5.0.26 doesn't work any more


Hi 
I upgrade mysql on win2000 from 5.0.18 to 5.0.26.

Inside my.ini I have this setup
# ------------
# Replica DB
# ------------
server-id=1
log-bin=pmv_manager_log_bin
relay-log=fep1-relay-bin
replicate-ignore-table=pmv_manager.parametri_configurazione
replicate-ignore-table=pmv_manager.lista_fep
replicate-ignore-table=pmv_manager.stato_fep_slave
replicate-ignore-table=pmv_manager.debug_log

At startup I get the following error:
061023 15:48:24  InnoDB: Started; log sequence number 0 266563613
061023 15:48:24 [ERROR] Error reading master configuration
061023 15:48:24 [ERROR] Failed to initialize the master info structure
061023 15:48:24 [Note] c:\Programmi\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready 
for connect

Also whe I try to setup the master_host with the command:
change master to master_host='';

I get the error "061023 16:01:01 [ERROR] Error reading master configuration" in 
the err log.

With the old revision of mysql all this works fine.
Someone of you have a problem like this and mybe some suggestions on how solve 
it ??

regrds, Enzo

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

Reply via email to