0034-CM启动报InnoDB engine not found分析

发布时间:2020-04-21 00:30:06 作者:Hadoop实操
来源:网络 阅读:469

温馨提示:要看高清无码套图,请使用手机打开并单击图片放大查看。

1.问题描述

cloudera-scm-server服务启动失败,日志报错如下:

2017-09-10 10:23:47,267 ERROR main:com.cloudera.enterprise.dbutil.DbUtil: InnoDB engine not found. Show engines reported: [MRG_MYISAM, CSV, MyISAM, MEMORY]
2017-09-10 10:23:47,268 ERROR main:com.cloudera.server.cmf.bootstrap.EntityManagerFactoryBean: InnoDb engine isn't present or enabled. SCM requires InnoDb MySQL db engine.

0034-CM启动报InnoDB engine not found分析

2.问题复现

测试环为CDH5.12.1,以下为复现步骤。

  1. 将/tmp目录修改为755权限
[root@ip-172-31-6-148 /]# chmod 755 tmp/
[root@ip-172-31-6-148 /]# ll
total 116
drwxr-xr-x. 231 root root 20480 Sep 10 15:48 tmp
[root@ip-172-31-6-148 /]# 

0034-CM启动报InnoDB engine not found分析

2.重启mysql服务

[root@ip-172-31-6-148 /]# service mysqld restart
Stopping mysqld:                                           [  OK  ]
Starting mysqld:                                           [  OK  ]
[root@ip-172-31-6-148 /]# 

0034-CM启动报InnoDB engine not found分析

3.启动cloudera-scm-server服务

[root@ip-172-31-6-148 /]# service cloudera-scm-server restart
Stopping cloudera-scm-server:                               [  OK  ]
Starting cloudera-scm-server:                               [  OK  ]
[root@ip-172-31-6-148 /]#

4.查看启动日志报错如问题描述一致

0034-CM启动报InnoDB engine not found分析

3.解决方法

将/tmp目录权限修改为777,重启mysql和cloudera-scm-server服务

  1. 修改/tmp目录权限为777
[root@ip-172-31-6-148 /]# chmod 777 tmp/
[root@ip-172-31-6-148 /]# ll
total 116
drwxrwxrwx. 231 root root 20480 Sep 10 15:48 tmp
[root@ip-172-31-6-148 /]# 

0034-CM启动报InnoDB engine not found分析

2.重启msyql服务

[root@ip-172-31-6-148 /]# service mysqld restart
Stopping mysqld:                                           [  OK  ]
Starting mysqld:                                           [  OK  ]
[root@ip-172-31-6-148 /]# 

0034-CM启动报InnoDB engine not found分析

3.重启cloudera-scm-server服务

[root@ip-172-31-6-148 /]# service cloudera-scm-server restart
Stopping cloudera-scm-server:                               [  OK  ]
Starting cloudera-scm-server:                               [  OK  ]
[root@ip-172-31-6-148 /]#

CM正常启动,问题解决。

4.备注

登录mysql通过show engines命令查看mysql引擎

mysql> show engines;
+------------+---------+------------------------------------------------------------+--------------+------+------------+
| Engine     | Support | Comment                                                    | Transactions | XA   | Savepoints |
+------------+---------+------------------------------------------------------------+--------------+------+------------+
| MRG_MYISAM | YES     | Collection of identical MyISAM tables                      | NO           | NO   | NO         |
| CSV        | YES     | CSV storage engine                                         | NO           | NO   | NO         |
| MyISAM     | DEFAULT | Default engine as of MySQL 3.23 with great performance     | NO           | NO   | NO         |
| InnoDB     | YES     | Supports transactions, row-level locking, and foreign keys | YES          | YES  | YES        |
| MEMORY     | YES     | Hash based, stored in memory, useful for temporary tables  | NO           | NO   | NO         |
+------------+---------+------------------------------------------------------------+--------------+------+------------+
5 rows in set (0.00 sec)

mysql> 

0034-CM启动报InnoDB engine not found分析

注意:如果没有显示InnoDB Engine可能是/tmp目录权限不足导致,也可能是源码编译的时候未编译InnoDB引擎;

mysql> show plugins;
+------------+--------+----------------+---------+---------+
| Name       | Status | Type           | Library | License |
+------------+--------+----------------+---------+---------+
| binlog     | ACTIVE | STORAGE ENGINE | NULL    | GPL     |
| partition  | ACTIVE | STORAGE ENGINE | NULL    | GPL     |
| CSV        | ACTIVE | STORAGE ENGINE | NULL    | GPL     |
| MEMORY     | ACTIVE | STORAGE ENGINE | NULL    | GPL     |
| InnoDB     | ACTIVE | STORAGE ENGINE | NULL    | GPL     |
| MyISAM     | ACTIVE | STORAGE ENGINE | NULL    | GPL     |
| MRG_MYISAM | ACTIVE | STORAGE ENGINE | NULL    | GPL     |
+------------+--------+----------------+---------+---------+
7 rows in set (0.00 sec)
mysql> 

0034-CM启动报InnoDB engine not found分析

如果没有InnoDB则可以通过INSTALL命令安装

查看mysql插件安装目录

mysql> show variables like 'plugin_dir'; 
+---------------+-------------------------+
| Variable_name | Value                   |
+---------------+-------------------------+
| plugin_dir    | /usr/lib64/mysql/plugin |
+---------------+-------------------------+
1 row in set (0.00 sec)

0034-CM启动报InnoDB engine not found分析

查看linux目录下是否有ha_innodb*.so的文件

[root@ip-172-31-6-148 ~]# cd /usr/lib64/mysql/plugin 
[root@ip-172-31-6-148 plugin]# ll
total 1416
lrwxrwxrwx 1 root root      25 Sep 10 15:47 ha_innodb_plugin.so -> ha_innodb_plugin.so.0.0.0
lrwxrwxrwx 1 root root      25 Sep 10 15:47 ha_innodb_plugin.so.0 -> ha_innodb_plugin.so.0.0.0
-rwxr-xr-x 1 root root 1259136 Jan 26  2017 ha_innodb_plugin.so.0.0.0
[root@ip-172-31-6-148 plugin]# 

0034-CM启动报InnoDB engine not found分析

执行Install命令安装InnoDB引擎

mysql> INSTALL PLUGIN InnoDB SONAME 'ha_innodb_plugin.so';
Query OK, 0 rows affected (0.23 sec)

mysql>

0034-CM启动报InnoDB engine not found分析

如果没有ha_innodb_plugin.so文件则需要考虑重新编译InnoDB引擎。


醉酒鞭名马,少年多浮夸! 岭南浣溪沙,呕吐酒肆下!挚友不肯放,数据玩的花!

温馨提示:要看高清无码套图,请使用手机打开并单击图片放大查看。

推荐关注Hadoop实操,第一时间,分享更多Hadoop干货,欢迎转发和分享。

0034-CM启动报InnoDB engine not found分析
原创文章,欢迎转载,转载请注明:转载自微信公众号Hadoop实操

推荐阅读:
  1. SpringBoot中怎么启动Tomcat
  2. 怎么解决oracle中由于gipc导致某节点crs无法启动问题

免责声明:本站发布的内容(图片、视频和文字)以原创、转载和分享为主,文章观点不代表本网站立场,如果涉及侵权请联系站长邮箱:is@yisu.com进行举报,并提供相关证据,一经查实,将立刻删除涉嫌侵权内容。

cdh found 分析

上一篇:Html5 Rocks 镜像

下一篇:监听日志过大,处理办法

相关阅读

您好,登录后才能下订单哦!

密码登录
登录注册
其他方式登录
点击 登录注册 即表示同意《亿速云用户服务条款》