Bug #27686 while setting log-bin MySQL Failed.

• Submitted: 6 Apr 2007 12:00
• Modified: 7 May 2007 4:46
• Reporter: Rahul Chaudhari
• Status: Closed
• Category: MySQL Server: Replication
• Severity: S2 (Serious)
• Version: MySQL5.0.27
• OS: Linux
• CPU Architecture: Any

[6 Apr 2007 12:00] Rahul Chaudhari

Description:
Hi All,

   I want to start Replication for my production database. I'm Having MySQL version 5.0.27.

   I'm setting my.cnf as followed

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

binlog-do-db=dotproject
log-bin=/etc/mysql/log_bin.log
server-id=1

  So problem start here, As i'm commenting the (#log-bin=/etc/mysql/log_bin.log)
and restarting MySQl with my.cnf it will start but when i'm removing the comment the service for mysql will never start and i have to again comment the bin-log location.

  I want to start the Replication process for MySQL database. but untill i'm setting log-bin i can't start the replication....

  Please help me in this case.

Regards,
 Rahul Chaudhari

How to repeat:
vi my.cnf

#make a comment over 
#bin-log=/home/mysql/bin-log.log

:wq

[root@granddb etc]# /etc/init.d/mysql restart
Shutting down MySQL.                                       [  OK  ]
Starting MySQL...................................          [  OK  ]
[root@granddb etc]#

vi my.cnf 

#when i'm removing the comment from bin-log
bin-log=/home/mysql/bin-log.log

[root@granddb etc]# /etc/init.d/mysql restart
Shutting down MySQL.                                       [  OK  ]
Starting MySQL...................................          [FAILED]
[root@granddb etc]#

why the service doesn't start ?

[6 Apr 2007 14:00] Valeriy Kravchuk

Thank you for a problem report. Please, try to repeat with a newer version, 5.0.37, and, in case of the same problem, send your entire error log.

[6 May 2007 23:00] Bugs System

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".

[7 May 2007 4:46] Rahul Chaudhari

Hi All,

  Thanks for a Help from MySQL.com  I was using 5.0.27 version of mysql, Now i'm using 5.0.37 version. My porblem got resolved by this version. 

Regards,
 Rahul Chaudhari

[6 Jan 2014 6:40] Julie Liu

I have exactly the same problem now. Mysql Server version: 5.1.71