MySQL Bugs: #16269: Failed to open the relay log

Bug #16269	Failed to open the relay log
Submitted:	6 Jan 2006 22:31	Modified:	10 Feb 2006 8:14
Reporter:	Frank Reiss	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	4.1.7	OS:	Linux (redhat es4)
Assigned to:		CPU Architecture:	Any

Description:
I have changed the names of my servers and am recieving isth message in my error_log file.

Version: '4.1.7-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
060106 14:35:09 [ERROR] Failed to open the relay log './localhost-relay-bin.000004' (relay_log_pos 2554)
060106 14:35:09 [ERROR] Could not find target log during relay log initialization
060106 14:37:31 [ERROR] Failed to open the relay log './localhost-relay-bin.000004' (relay_log_pos 2554)
060106 14:37:31 [ERROR] Could not find target log during relay log initialization
A mysqld process already exists at  Fri Jan 6 15:10:53 CST 2006

Is this a bug or does some one know how to fix the problem with out havinb to reinstall the mysql server software?

Also note that I can not login to the database from another system also:
[root@imp-vm-rhes4-1d etc]# mysql radius -h=imp-vm-rhes4-2d -u=root -p
Enter password: 
ERROR 2005 (HY000): Unknown MySQL server host '=imp-vm-rhes4-2d' (1)

the directory /var/lib/mysql has the following files in it.
ibdata1           imp-vm-rhes4-1d-relay-bin.000008  localhost-relay-bin.000004
ib_logfile0       imp-vm-rhes4-1d-relay-bin.000009  localhost-relay-bin.index
ib_logfile1       imp-vm-rhes4-1d-relay-bin.000010  master.info
imp-vm-rhes4-1d-relay-bin.000001  imp-vm-rhes4-1d-relay-bin.000011  mysql
imp-vm-rhes4-1d-relay-bin.000002  imp-vm-rhes4-1d-relay-bin.000012  mysql.sock
imp-vm-rhes4-1d-relay-bin.000003  imp-vm-rhes4-1d-relay-bin.000013  radius
imp-vm-rhes4-1d-relay-bin.000004  imp-vm-rhes4-1d-relay-bin.000014  relay-log.info 
imp-vm-rhes4-1d-relay-bin.000005  imp-vm-rhes4-1d-relay-bin.000015  test
imp-vm-rhes4-1d-relay-bin.000006  imp-vm-rhes4-1d-relay-bin.000016
imp-vm-rhes4-1d-relay-bin.000007  imp-vm-rhes4-1d-relay-bin.index

How to repeat:
1) this problem is on 4 of my systems in which I have changed the names.

Frank, 
1) what makes you believe it's mysql administrator bug? I'd set category as 'server'
2) you shouldn't use '=' for options -h and -u. So, your command line for connection must be 
mysql radius -h imp-vm-rhes4-2d -u root -p
(Please submit every problem to separate bug report)
3) I would note 4.1.7 is pretty old version.

Do you use replications?

Hi,

I am trying to set up replication on the new redhat es4 systems that came with the systems.

1) the hostname changed for my sql from localhost to the systems names when I added the addresses into the /etc/hosts file.

2) Replications is not working on this version I think that is a setup issue. I did have it working in a test fedora core setup that I have. any tips on replication setup would also be appreciated.

I am down loading a ner version of my sql for testing purposes now.

Please note that I am new to redhat and mysql.

Also I did try the attach string and it failed also.

Frank

We're sorry, but the bug system is not the appropriate forum for 
asking help on using MySQL products. Your problem is not the result 
of a bug.

Support on using our products is available both free in our forums
at http://forums.mysql.com and for a reasonable fee direct from our
skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.

Additional info:

It really looks like your configuration problem, not a bug in MySQL code. Why do you think it is a bug?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".