Mysql Error 1186 Hy000 Binlog Closed Cannot Reset Master
you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. + Reply to Thread Results 1 to 1 of 1 Thread: Disabling MySQL binlogs Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode February 17th, 2009,01:08 PM #1 geoffrey View Profile View Forum Posts Private Message Senior Member Join Date Aug 2008 Posts 415 Disabling MySQL binlogs In large customer installations, we sometimes see the MySQL binary logs growing large. This can take up significant amounts of space in the data directory. As Infobright does not directly use these logs, here are some tips on how to turn them off and/or clean out the ones you already have. The binary logs are located under the data directory, and have names like "mysql-bin.xxxxxx" where xxxxxx is some number. To clean them up: 1) Log into the MySQL prompt as "root" Code: bash$ mysql-ib -u root 2) Issue the command at the mysql> prompt: Code: mysql> reset master; If you get an error saying, "ERROR 1186 (HY000): Binlog closed, cannot RESET MASTER", this means binlogs are already disabled. 3) To disable them: Edit the /etc/my-ib.cnf file and comment out the "log-bin" line: Code: # log-bin=mysql-bin and restart mysqld. Geoffrey Reply With Quote + Reply to Thread Quick Navigation Technical Tips & Tricks Top Site Areas Settings Private Messages Subscriptions Who's Online Search Forums Forums Home Forums General Forum Community Banter Infobright Community Edition ICE Engine Design Discussion ICE Feature Requests ICE Q&A Webinar Q&A Infobright Coding Competition Community Solutions Jaspersoft / ICE Integrated Virtual Machine Pentaho / ICE Integrated Virtual Machine BIRT/Actuate and ICE Virtual Machine BI Tool Integration ETL / Load Processing Technical Tips & Tricks Data Warehousing General Discussion "How to..." Discussion Vertical Applications New Methodologies at the Edge of Academic and Industry Research « Previous Thread | Next Thread » Posting Permissions You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is On HTML code is Off Forum Rules Contact Us The Open Source Analaytic Database Community Archive Privacy Statement Terms of Service Top Back to top Powered by vBulletin Version 4.1.5 Copyright &c
Community Podcasts MySQL.com Downloads Documentation Section Menu: MySQL Forums :: Replication :: binary update log does not work New Topic Advanced Search binary update log does not work Posted by: Jesus Rafael Lopez Ibarra () Date: April 29, 2011 10:14AM Hello i have a problem with the binary log i does not work. i test the binary los with the 'test' database, and worked ok. on /etc/my.cnf ------ log-bin=db_change_log binlog-do-db=test max_binlog_size=1M ------ then 1- i load another database 2- configured it to binary update logging (on my.cnf) and deleted the configuration of the 'test' database (erased 'log-bin=test' and added 'log-bin=other') 3- i also added (on my.cnf) server-id=12345 and (wich i dunno why for) innodb_flush_log_at_trx_commit=1 sync_binlog=1 4 https://www.infobright.com/forums/showthread.php?5764-Disabling-MySQL-binlogs then I REMOVE manually the old test log files and the log.index from /var/lib/mysql, in order to leave only the new ones of the new database. rm db_change_log.000001 rm db_change_log.000002 rm db_change_log.index then continued trying to set up replication, in some point i realized that the binary loggin was not working anymore on master (i just started to configure slave, but i did not finish) even if i change the databse, then i reinstall mysql, http://forums.mysql.com/read.php?26,418197,418197 then i update my OS (fedora 13 , command line acces),reinstall mysql and nothing this instruction returns msyql> show master status; Empty set(0.00)sec and this one mysql> reset master; ERROR 1186 (HY000): Binlog closed, cannot RESET MASTER but binary update loggin does not work!! i dunno what to do to solve the problem. this server will be on production enviroment some weeks more. thanks for helping Navigate:Previous Message•Next Message Options:Reply•Quote Subject Views Written By Posted binary update log does not work 5784 Jesus Rafael Lopez Ibarra 04/29/2011 10:14AM Re: binary update log does not work 1806 Jesus Rafael Lopez Ibarra 04/29/2011 10:21AM Re: binary update log does not work 1415 Jesus Rafael Lopez Ibarra 04/29/2011 12:24PM Sorry, you can't reply to this topic. It has been closed. powered by phorum 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. Contact Sales USA: +1-866-221-0634 Canada: +1-866-221-0634 Germany: +49 89 143 01280 France: +33 1 57 60 83 57 Italy: +39 02 249 59 120 UK: +44 207 553 8447 Japan: 0120-065556 China: 10800-811-0823 India: 0008001005870 More Countries» Contact Us Online» Products MySQL Enterprise Edition MySQL Standard Edition MySQL Classic Edition MySQL Cluster CGE MySQL Embedded (OEM/ISV) Services Training C
成立QQ群、微信群,辅助互动与技术同行交流 首页 | 博文目录 | 关于我 goolen 博客访问: 406723 博文数量: 152 用 户 组: 普通用户 注册时间: 2011-10-20 18:17 个人简介 技术交流群: 241756225 文章分类 全部博文(152) Oracle(83) Mysql(44) Linux(8) Goldengate(3) Mongodb(2) 监控系统(11) Greenplum(1) 未分配的博文(0) 最近访客 http://blog.itpub.net/23249684/viewspace-1386182/ royevict xinxin41 糗_蘑菇 wwwlby 静以致远 依然wana heu tom555ca tolilong http://iderror.com/tag/how-to-fix-this-error-1186-hy000-binlog-closed-cannot-reset-master/ 微信关注 IT168企业级官微 微信号:IT168qiye 系统架构师大会 微信号:SACC2013 订阅 推荐博文 ·Oracle 12c Data Guard搭建(... ·Oracle Real Time SQL Monito... ·11g升级到Oracle 12c碰到的问... ·Oracle 12c PDB迁移(一)... ·使用Out of Place升级策略进... 热词专题 友情链接 ·老杨 ·老熊 ·惜分飞 ·夜无伤 ·Dave ·Lunar ·MacleanLiu ·落落 ·eygle ·Roger ERROR mysql error 1186 (HY000): Binlog closed, cannot RESET MASTER 2014-12-31 15:27:40 分类: MySQL
想把一台mysql slave切换成主库的时候报错: mysql> reset slave; ERROR 1198 (HY000): This operation cannot be performed with a running slave; run STOP SLAVE first mysql> stop slave; Query OK, 0 rows affected (0.00 sec) mysql> reset master; ERROR 1186 mysql error 1186 (HY000): Binlog closed, cannot RESET MASTER 这是因为slave配置文件中注释了log-bin参数导致的,编辑my.cnf,设置log-bin=参数 重启mysql服务: [root@test11g ]# /etc/init.d/mysqld restart Shutting down MySQL.. [ OK ] Starting MySQL.. [ OK ] mysql> stop slave; Query OK, 0 rows affected (0.09 sec) mysql> reset master; Query OK, 0 rows affected (0.00 sec) 阅读(5479) | 评论(0) | 转发(0) | 0 上一篇:exp导出命令query参数指定的where条件里符号也要转义 下一篇:Can't open and lock privilege tables: Table 'mysql.user' doesn't exist 相关热门文章 MySQL数据库引擎快速指导... linux下phpBB+Oracle解决方案,... MySQL中修改密码及访问限制设... IIS下配置 Mantis+PHP+MYSQL环... linux下 MYSQL 定时备分 用磁盘阵列做raid10时,盘越多... 如何获取给定时间的当周的星期... 关于alter session的语句,怎... 【体系结构】有关Oracle SCN知... 请教如何查询两表间符合条件的... 给主人留下些什么吧!~~ 评论热议 请登录后评论。 登录 注册 盛拓传媒简介 | 关于IT168 | 合作伙伴 | 广告服务 | 使用条款 | 投稿指南 | 诚聘精英 | 联系我们 | 苹果论坛 | 网站导航 |to ORA-00899ORA-00900 to ORA-01499ORA-01500 to ORA-02099ORA-02100 to ORA-04099ORA-04100 to ORA-07499ORA-07500 to ORA-09857ORA-09858 to ORA-12299ORA-12300 to ORA-12399ORA-12400 to ORA-12699ORA-12700 to ORA-19399ORA-19400 to ORA-24279ORA-24280 to ORA-29249ORA-29250 to ORA-32799ORA-32800 to ORA-32999ORA-33000 to ORA-65535ORADB-AMDORADB-AUDORADB-DBVORADB-DRGORADB-EPCORADB-EXPORADB-IMGORADB-IMPORADB-KUPORADB-LCDORADB-LFIORADB-LPXORADB-LRMORADB-LSXORADB-MODORADB-NCRORADB-NIDORADB-NMPORADB-NNCORADB-NNFORADB-NNLORADB-NNOORADB-NPLORADB-NZEORADB-O2FORADB-O2IORADB-O2UORADB-PCBORADB-PCCORADB-PLSORADB-QSMORADB-RMANORADB-SQLORADB-TNSORADB-VIDWeblogic 10.3WL103-ApiWL103-ApplicationPollerWL103-BridgeWL103-BugReporterWL103-CacheWL103-ClusterWL103-ClusterExtensionWL103-CommonWL103-ConfigWL103-ConnectorWL103-ConsoleServicesWL103-CustomModuleWL103-DatabaseLessLeasingWL103-DebugModuleWL103-DeployerRuntimeWL103-DeploymentManagerWL103-DeploymentServiceWL103-DiagnosticsWL103-DiagnosticsHarvesterWL103-DiagnosticsInstrumentorWL103-DiagnosticsWatchWL103-DRSWL103-EJBWL103-EngineWL103-EntitlementWL103-FastSwapWL103-HarvesterJMXWL103-HealthWL103-HTTPWL103-HTTPSessionWL103-IIOPWL103-JDBCWL103-JMSWL103-JMSClientExceptionWL103-JMSExceptionWL103-JMXWL103-JNDIWL103-KernelWL103-LogMgmtWL103-ManagementWL103-MasterDeployerWL103-MBeanTypingUtilWL103-MessagingWL103-MIExceptionWL103-NetWL103-NodeManagerWL103-PathWL103-PubSubWL103-PubSubJmsWL103-RMIWL103-SAFWL103-SecurityWL103-ServerWL103-ServiceWL103-SingletonWL103-SlaveDeployerWL103-SNMPWL103-SocketWL103-SPIDeployerWL103-StoreWL103-T3MiscWL103-T3SrvrWL103-TXWL103-TXExceptionWL103-WebServiceWL103-WLSConsoleWL103-WorkManagerWL103-WTCWL103-XMLWebLogic 9.2WL92-ApplicationPollerWL92-BridgeWL92-BugReporterWL92-ClusterWL92-CommonWL92-ConfigWL92-ConnectorWL92-ConsoleServicesWL92-CustomModuleWL92-DeployerRuntimeWL92-DeploymentManagerWL92-DeploymentServiceWL92-DiagnosticsWL92-DRSWL92-EJBWL92-EntitlementWL92-HealthWL92-HTTPWL92-HTTPSessionWL92-IIOPWL92-JDBCWL92-JMSWL92-JMSClientExceptionWL92-JMSExceptionWL92-JMXWL92-JNDIWL92-KernelWL92-LogMgmtWL92-Man