Mysql Error Binlog Has Bad Magic Number
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Binlog has bad magic number up vote 5 down vote favorite I keep getting this error whenever I start MySQL. 121028 1:38:55 [Note] Plugin 'FEDERATED' is disabled. 121028 1:38:55 InnoDB: The InnoDB memory heap is disabled 121028 1:38:55 InnoDB: Mutexes and rw_locks use Windows interlocked functions 121028 1:38:56 InnoDB: Compressed tables use zlib 1.2.3 121028 1:38:56 InnoDB: Initializing buffer pool, size = 16.0M 121028 1:38:56 InnoDB: Completed initialization of buffer pool 121028 1:38:56 InnoDB: highest supported file format is Barracuda. 121028 1:38:57 InnoDB: Waiting for the background threads to start 121028 1:38:58 InnoDB: 1.1.8 started; log sequence number 3137114 121028 1:38:58 [ERROR] Binlog has bad magic number; It's not a binary log file that can be used by this version of MySQL 121028 1:38:58 [ERROR] Can't init tc log 121028 1:38:58 [ERROR] Aborting 121028 1:38:58 InnoDB: Starting shutdown... 121028 1:38:58 InnoDB: Shutdown completed; log sequence number 3137114 121028 1:38:58 [Note] C:\PROGRA~2\EASYPH~1.1\MySql\bin\mysqld.exe: Shutdown complete I have already tried this. I have an EasyPHP 12.1 setup on Windows 7x64 PC. mysql windows binlog share|improve this question edited Oct 28 '12 at 1:36 RolandoMySQLDBA 108k15139276 asked Oct 27 '12 at 20:16 laggingreflex 12813 add a comment| 1 Answer 1 active oldest votes up vote 6 down vote accepted Binary logs have different start positions upon the creation of a new binary log. In fact, a binary log positio
Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. [SOLVED] Binlog has bad magic number Started by mrrush101, Jun 09 2009 06:06 PM Please log in to reply 2 replies to this topic #1 mrrush101 mrrush101 Newbie New Members 2 posts Posted 09 June 2009 - 06:06 PM I cant connect to my Mysql database anymore. I checked this log and found this error message below. 090608 23:41:19 InnoDB: Started; log sequence number 0 43655090608 23:41:19 [ERROR] Binlog has bad magic number; It's not a binary log file that can be used by this version of MySQL090608 23:41:19 [ERROR] Can't init http://dba.stackexchange.com/questions/27749/binlog-has-bad-magic-number tc log090608 23:41:19 [ERROR] AbortingI have been working on my website for weeks and I am about to snap. I copied the original php5 and the msql5 folders then reinstalled myssql and php5. Everything works great except the fact my tables are no longer there so i copied the php5 and mysql folers that i originaly had over the the directory and am getting the old error message again. Is there a way to install a https://forums.phpfreaks.com/topic/161550-solved-binlog-has-bad-magic-number/ clean copy then somehow import my tables to the new database? I did not make a backup copy of the original database using mysql backup. I did not do this because I was not done finishing in the site. There must be some other file that holds that info so i can import it to the new setup?Is there a way to fix the error message? If so maybe I can get things back to the way they were. I have spent weeks on the site with custom info. I really need to get this back.Any help would be greatly appreciated. ThanksAny help would be appreciated greatly-------------------------------------------------------------------------------- Back to top #2 gassaz gassaz Advanced Member Members 61 posts Posted 09 June 2009 - 09:06 PM A crazy idea:stop the serviceDelete or move the log filesstart the serviceWhen you start the service MySql will try to make a new log file.. I used this when i got corrupted the ib_logfile0... Back to top #3 mrrush101 mrrush101 Newbie New Members 2 posts Posted 10 June 2009 - 02:05 AM I cant thank you enough. Thanks Thanks Thanks, LOL Your crazy Idea worked. You saved me so much time and aggravation Back to top Back to MySQL Help · Next Unread Topic → 0 user(s) are reading this topic 0 members, 0 guests, 0 anonymous users Reply to qu
are getting https://lists.mysql.com/replication/2158 the below replication error Last_SQL_Errno: 1593 https://bugs.mysql.com/bug.php?id=57801 Last_SQL_Error: *Error initializing relay log position: Binlog has bad magic number; It's not a binary log file that can be used by this version mysql error of MySQL.* Initially we were facing the below error, which we skipped that resulted the above error. Last_Error: Could not execute Update_rows event on tables xxxxxxx.zzzzz: Can't find record in mysql error binlog 'zzzzz', Error_code:1032; handle error HA_ERR_KEY_NOT_FOUND; the event's master log mysql-binlog-LLL01.000683, end_log_pos 776331958. Please do help!...... Thread• Binlog has bad magic number errorKamalakarReddyY22Aug • Re: Binlog has bad magic number errorMatsKindahl29Aug © 1995, 2016, Oracle Corporation and/or its affiliates Legal Policies Your Privacy Rights Terms of Use Contact Us Page generated in 0.008 sec. Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.
Reporter: Kim Carlsen Email Updates: Status: No Feedback Impact on me: None Category:MySQL Server: Replication Severity:S3 (Non-critical) Version:5.1.51 OS:Any Assigned to: Assigned Account Tags: binlog, flush logs, mysqldump, slave stop View Add Comment Files Developer Edit Submission View Progress Log Contributions [28 Oct 2010 11:07] Kim Carlsen Description: It seems that when flushing logs (and rotating binary log) the slave has a chance to stop, with an error complaining that the binary log is not valid (see below). But Im not sure how and when this happens. Error on the slave: 101028 2:19:59 [ERROR] Error reading packet from server: Binlog has bad magic number; It's not a binary log file that can be used by this version of MySQL ( server_errno=1236) 101028 2:19:59 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'Binlog has bad magic number; It's not a binary log file that can be used by this version of MySQL', Error_code: 1236 101028 2:19:59 [Note] Slave I/O thread exiting, read up to log 'cactus-binlog.001309', position 4 This happened right between when our backup of db1 finished and backup of db2 started. Our backup script, the extra file just contains the password: /usr/local/bin/mysqldump --defaults-extra-file=/home/backups/my.cnf --routines -F --skip-lock-tables --single-transaction -ubackup db1 | gzip > /home/backups/mysql/db1.$TIMESTAMP.sql.gz /usr/local/bin/mysqldump --defaults-extra-file=/home/backups/my.cnf --routines -F --skip-lock-tables --single-transaction -ubackup db2 | gzip > /home/backups/mysql/db2.$TIMESTAMP.sql.gz Timestamp of our backup files 10010157919 Oct 28 02:19 db1.10-28-10-0100.sql.gz 315762511 Oct 28 02:22 db2.10-28-10-0100.sql.gz How to repeat: I cant repeat this, but every now and then, the slave stops with this error. [28 Oct 2010 11:09] Kim Carlsen The slave still works, just need a 'start slave' command and it will