Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 313
  • Last Modified:

Cant start binary logging with mysql 5.1 community editon

I'm trying to start binary logging using MySQL 5.1-73 community edition.  I'm following the documentation and the only thing that appears to be needed is adding --log-bin="c:\MySQL logs\bin_log" to the startup parameters.  (On a side note I couldn't set these in services, I had to edit the registry).  However it won't start up.  I've tried copying the command string out of the registry to the command prompt and running it.  It works without the log-bin argument, but fails to start with it applied.

The command line looks like:
"C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" --defaults-file="C:\Program Files\MySQL\MySQL Server 5.1\my.ini" --bin-log="c:\MySQL logs\bin_log" MySQL

It does get far enough to create an index file.  There is one new log entry in the event log:
Event id 100: Aborting

Not terribly useful.

The docs says that there are reasonable defaults for all of the other options, and I'm fine with those.
We are using INNODB and the transaction isolation level is set to repeatable-read.

Am I doing something wrong here, or is this a function that's not available in my situation?
0
geekdad1
Asked:
geekdad1
1 Solution
 
StampelCommented:
Edit "C:\Program Files\MySQL\MySQL Server 5.1\my.ini",  and set this into the mysqld section :
server-id=1
log-bin=mysqld-bin
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now