无法启动mysql服务,发生错误1067的解决办法?
Posted
tags:
篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了无法启动mysql服务,发生错误1067的解决办法?相关的知识,希望对你有一定的参考价值。
进入mysql的安装文件夹找到my.ini ;
里面有一句:default-storage-engine=INNODB改成MYISAM;
再去开启MySql服务就能够顺利开启了。
MySQL是一个关系型数据库管理系统,由瑞典MySQL AB 公司开发,目前属于 Oracle 旗下产品。MySQL 是最流行的关系型数据库管理系统之一,在 WEB 应用方面,MySQL是最好的 RDBMS (Relational Database Management System,关系数据库管理系统) 应用软件。
MySQL是一种关系数据库管理系统,关系数据库将数据保存在不同的表中,而不是将所有数据放在一个大仓库内,这样就增加了速度并提高了灵活性。
MySQL所使用的 SQL 语言是用于访问数据库的最常用标准化语言。MySQL 软件采用了双授权政策,分为社区版和商业版,由于其体积小、速度快、总体拥有成本低,尤其是开放源码这一特点,一般中小型网站的开发都选择 MySQL 作为网站数据库。
参考技术A
这是因为在拷贝的过程中将mysql/data中的数据库都删掉了,其中有个mysql数据库不可删,重新把这个文件夹拷贝过来问题就解决了。
具体操作步骤:
方法一:
1、打开my.ini文件,找到default-storage-engine=InnoDB这一行,把它改成default-storage-engine=MyISAM。
2、删除在MySQL安装目录下的Data目录中的ib_logfile0和ib_logfile1
3、找到在配置MySQL服务器时指定的InfoDB目录删除掉ibdata1
根据my.ini文件中:
#*** INNODB Specific options *** innodb_data_home_dir="D:/"
4、重新启动MySQL的Service
方法二:
重装mysql时,一直提示“无法启动MYSQL服务,错误1067进程意外终止 重启,修复注册表都没什么用, 网上查了,改什么basedir,也没用,我用的是mysql5.8,找来找去,想起之前装了wampserver,pc_webserver等集成环境, 此些软件会把my.ini, php.ini 写入C:WINDOWS目录下,并设为只读。
解决方法:
把windows目录下,my.ini文件删除,重装mysql,服务启动成功
方法三:
1、执行winmysqladmin,生成my.ini文件
2、mysqld -install 启动mysql服务
3、net start mysql 启动mysql服务显示正常 当通过mysql -u root -p 连接时候报服务器没有启动的错误,察看server服务,确实mysql服务没有启动,手动启动产生1067错误,重新安装过几次mysql,错误依旧。察看各个配置都没有错误。
我的系统环境 win2003 mysql版本4.0.12 解决办法,将winmysqladmin生成的my.ini拷贝到c:windows下再启动mysql就一切OK了。 这个没试过 。其实不需要重新配置 你只要在/bin 目录下依次点击 mysql.exe
mysqld.exe
mysqld-nt.exe
winmysqladmin.exe
提示框出现后 直接cancle 掉
然后再点击 winmysqladmin.exe 在右下脚那个小图标上 选择启动服务就可以了。
mysql-5.7.9-winx64 MySQL服务无法启动,服务没有报告任何错误的解决办法 转自IT精英团:http://www.itnpc.com/news/web/1448328182270
最新解压版本的mysql 解压安装的时候报错
D:\mysql-5.7.9-winx64\bin>net start mysql
MySQL 服务正在启动 .
MySQL 服务无法启动。
服务没有报告任何错误。
mysql下面是没有data文件夹的,此文件夹不需要自己建。
D:\mysql-5.7.9-winx64\bin>mysqld --console
2015-11-23T14:46:03.711082Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-11-23T14:46:03.711082Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2015-11-23T14:46:03.711583Z 0 [Note] mysqld (mysqld 5.7.9) starting as process 9984 ...
2015-11-23T14:46:03.716585Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-23T14:46:03.717086Z 0 [Note] InnoDB: Uses event mutexes
2015-11-23T14:46:03.717591Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2015-11-23T14:46:03.721090Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-23T14:46:03.726596Z 0 [Note] InnoDB: Number of pools: 1
2015-11-23T14:46:03.727094Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-23T14:46:03.764098Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2015-11-23T14:46:03.774101Z 0 [Note] InnoDB: Completed initialization of buffer pool
2015-11-23T14:46:03.805645Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-23T14:46:03.832178Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2015-11-23T14:46:03.832679Z 0 [Note] InnoDB: Setting file ‘.\ibtmp1‘ size to 12 MB. Physically writing the file full; Please wait ...
2015-11-23T14:46:03.924164Z 0 [Note] InnoDB: File ‘.\ibtmp1‘ size is now 12 MB.
2015-11-23T14:46:03.926664Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2015-11-23T14:46:03.927165Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2015-11-23T14:46:03.929749Z 0 [Note] InnoDB: Waiting for purge to start
2015-11-23T14:46:03.988759Z 0 [Note] InnoDB: 5.7.9 started; log sequence number 1209980
2015-11-23T14:46:03.990259Z 0 [Note] InnoDB: not started
2015-11-23T14:46:03.990759Z 0 [Note] InnoDB: Loading buffer pool(s) from D:\mysql-5.7.9-winx64\data\ib_buffer_pool
2015-11-23T14:46:03.990759Z 0 [Note] Plugin ‘FEDERATED‘ is disabled.
2015-11-23T14:46:03.996731Z 0 [Note] InnoDB: Buffer pool(s) load completed at 151123 22:46:03
mysqld: Table ‘mysql.plugin‘ doesn‘t exist
2015-11-23T14:46:04.003002Z 0 [ERROR] Can‘t open the mysql.plugin table. Please run mysql_upgrade to create it.
2015-11-23T14:46:04.007005Z 0 [Warning] Gtid table is not ready to be used. Table ‘mysql.gtid_executed‘ cannot be opened.
2015-11-23T14:46:04.009510Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2015-11-23T14:46:04.015010Z 0 [Note] Server hostname (bind-address): ‘*‘; port: 3306
2015-11-23T14:46:04.016513Z 0 [Note] IPv6 is available.
2015-11-23T14:46:04.018012Z 0 [Note] - ‘::‘ resolves to ‘::‘;
2015-11-23T14:46:04.021520Z 0 [Note] Server socket created on IP: ‘::‘.
2015-11-23T14:46:04.029022Z 0 [Warning] Failed to open optimizer cost constant tables
2015-11-23T14:46:04.035027Z 0 [ERROR] Fatal error: Can‘t open and lock privilege tables: Table ‘mysql.user‘ doesn‘t exist
2015-11-23T14:46:04.037027Z 0 [ERROR] Aborting
2015-11-23T14:46:04.038528Z 0 [Note] Binlog end
2015-11-23T14:46:04.042030Z 0 [Note] Shutting down plugin ‘ngram‘
2015-11-23T14:46:04.045533Z 0 [Note] Shutting down plugin ‘partition‘
2015-11-23T14:46:04.048050Z 0 [Note] Shutting down plugin ‘BLACKHOLE‘
2015-11-23T14:46:04.050550Z 0 [Note] Shutting down plugin ‘ARCHIVE‘
2015-11-23T14:46:04.053037Z 0 [Note] Shutting down plugin ‘PERFORMANCE_SCHEMA‘
2015-11-23T14:46:04.053539Z 0 [Note] Shutting down plugin ‘MRG_MYISAM‘
2015-11-23T14:46:04.058545Z 0 [Note] Shutting down plugin ‘MyISAM‘
2015-11-23T14:46:04.059544Z 0 [Note] Shutting down plugin ‘INNODB_SYS_VIRTUAL‘
2015-11-23T14:46:04.063045Z 0 [Note] Shutting down plugin ‘INNODB_SYS_DATAFILES‘
2015-11-23T14:46:04.065547Z 0 [Note] Shutting down plugin ‘INNODB_SYS_TABLESPACES‘
2015-11-23T14:46:04.069049Z 0 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN_COLS‘
2015-11-23T14:46:04.073053Z 0 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN‘
2015-11-23T14:46:04.081560Z 0 [Note] Shutting down plugin ‘INNODB_SYS_FIELDS‘
2015-11-23T14:46:04.084060Z 0 [Note] Shutting down plugin ‘INNODB_SYS_COLUMNS‘
2015-11-23T14:46:04.086063Z 0 [Note] Shutting down plugin ‘INNODB_SYS_INDEXES‘
2015-11-23T14:46:04.088564Z 0 [Note] Shutting down plugin ‘INNODB_SYS_TABLESTATS‘
2015-11-23T14:46:04.100570Z 0 [Note] Shutting down plugin ‘INNODB_SYS_TABLES‘
2015-11-23T14:46:04.101071Z 0 [Note] Shutting down plugin ‘INNODB_FT_INDEX_TABLE‘
2015-11-23T14:46:04.103575Z 0 [Note] Shutting down plugin ‘INNODB_FT_INDEX_CACHE‘
2015-11-23T14:46:04.106077Z 0 [Note] Shutting down plugin ‘INNODB_FT_CONFIG‘
2015-11-23T14:46:04.109580Z 0 [Note] Shutting down plugin ‘INNODB_FT_BEING_DELETED‘
2015-11-23T14:46:04.118084Z 0 [Note] Shutting down plugin ‘INNODB_FT_DELETED‘
2015-11-23T14:46:04.120589Z 0 [Note] Shutting down plugin ‘INNODB_FT_DEFAULT_STOPWORD‘
2015-11-23T14:46:04.123088Z 0 [Note] Shutting down plugin ‘INNODB_METRICS‘
2015-11-23T14:46:04.127091Z 0 [Note] Shutting down plugin ‘INNODB_TEMP_TABLE_INFO‘
2015-11-23T14:46:04.130093Z 0 [Note] Shutting down plugin ‘INNODB_BUFFER_POOL_STATS‘
2015-11-23T14:46:04.132093Z 0 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE_LRU‘
2015-11-23T14:46:04.135097Z 0 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE‘
2015-11-23T14:46:04.137097Z 0 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX_RESET‘
2015-11-23T14:46:04.141601Z 0 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX‘
2015-11-23T14:46:04.144602Z 0 [Note] Shutting down plugin ‘INNODB_CMPMEM_RESET‘
2015-11-23T14:46:04.148106Z 0 [Note] Shutting down plugin ‘INNODB_CMPMEM‘
2015-11-23T14:46:04.151608Z 0 [Note] Shutting down plugin ‘INNODB_CMP_RESET‘
2015-11-23T14:46:04.154108Z 0 [Note] Shutting down plugin ‘INNODB_CMP‘
2015-11-23T14:46:04.158112Z 0 [Note] Shutting down plugin ‘INNODB_LOCK_WAITS‘
2015-11-23T14:46:04.166119Z 0 [Note] Shutting down plugin ‘INNODB_LOCKS‘
2015-11-23T14:46:04.169622Z 0 [Note] Shutting down plugin ‘INNODB_TRX‘
2015-11-23T14:46:04.171624Z 0 [Note] Shutting down plugin ‘InnoDB‘
2015-11-23T14:46:04.177629Z 0 [Note] InnoDB: FTS optimize thread exiting.
2015-11-23T14:46:04.182131Z 0 [Note] InnoDB: Starting shutdown...
2015-11-23T14:46:04.293551Z 0 [Note] InnoDB: Dumping buffer pool(s) to D:\mysql-5.7.9-winx64\data\ib_buffer_pool
2015-11-23T14:46:04.295552Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 151123 22:46:04
2015-11-23T14:46:05.445554Z 0 [Note] InnoDB: Shutdown completed; log sequence number 1209999
2015-11-23T14:46:05.447053Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2015-11-23T14:46:05.448554Z 0 [Note] Shutting down plugin ‘MEMORY‘
2015-11-23T14:46:05.449054Z 0 [Note] Shutting down plugin ‘CSV‘
2015-11-23T14:46:05.452556Z 0 [Note] Shutting down plugin ‘sha256_password‘
2015-11-23T14:46:05.458060Z 0 [Note] Shutting down plugin ‘mysql_native_password‘
2015-11-23T14:46:05.459061Z 0 [Note] Shutting down plugin ‘binlog‘
2015-11-23T14:46:05.463065Z 0 [Note] mysqld: Shutdown complete
D:\mysql-5.7.9-winx64\bin>mysqld --initialize
2015-11-23T14:49:00.783987Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-11-23T14:49:00.785988Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
2015-11-23T14:49:00.786989Z 0 [ERROR] Aborting
上面的错误是自己建了data文件夹之后 用 mysqld --initialize报错。
删除之前建的data文件夹,由mysql自己创建即可。
D:\mysql-5.7.9-winx64\bin>mysqld --initialize
D:\mysql-5.7.9-winx64\bin>net start mysql
MySQL 服务正在启动 .
MySQL 服务已经启动成功。
转自【IT精英团】:http://www.itnpc.com/news/web/144832818227054.html
以上是关于无法启动mysql服务,发生错误1067的解决办法?的主要内容,如果未能解决你的问题,请参考以下文章
关于无法启动MYSQL服务”1067 进程意外终止”解决办法
关于无法启动MYSQL服务”1067 进程意外终止”解决办法