启动Hive报错：Found class jline.Terminal, but interface was expected

最新推荐文章于 2024-05-25 11:13:16 发布
最新推荐文章于 2024-05-25 11:13:16 发布
阅读量1.1k 收藏
点赞数 1
CC 4.0 BY-SA版权
分类专栏： Hive 文章标签： Found class jline.Terminal bu
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/BigData_Mining/article/details/80097818
本文介绍了解决Hive与Hadoop YARN中jline版本不一致导致的问题。只需将Hive中的jline-2.12.jar替换到Hadoop的YARN lib目录下即可。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

这个错误是hive中的jline-2.12.jar这个jar包与hadoop中yarn中的lib下的这个jline-xxx.jar版本不一致造成的。只需要将hive中的这jline-2.12.jar包移动到hadoop的yarn中的lib下，替换掉原来的jar包就OK了。

Found class jline.Terminal, but interface was expected...
杨鑫newlife的专栏
07-07 2299
Found class jline.Terminal, but interface was expected...
hive 启动 报错Exception in thread "main" java.lang.IncompatibleClassChangeError: Found c interface was e
乔治大哥的博客
10-30 1860
[ERROR] Terminal initialization failed; falling back to unsupported java.lang.IncompatibleClassChangeError: Found class jline.Terminal, but in at jline.TerminalFactory.create(TerminalFactory.java:...
CDH5之Found class jline.Terminal, but interface was expected
crazy_stone0002的博客
04-15 151
一.背景: 公司CDH5集群已经部署完毕,需要通过web界面添加hive组件,一般来说通过web界面来添加,会报两个错误, 一个是配置hive的元数据的/usr/share/java/mysql-connect...
hive启动出错：Found class jline.Terminal, but interface was expected
小萌猿的博客
03-04 3627
启动hive时报错，如下图： 原因：hadoop与hive的jline包版本不一致造成 解决：在hadoop安装路径下的share/hadoop/yarn/lib找到jline-xxx.jar 在hive路径下的lib里也找到jline-xxx.jar，会发现这两个包版本不一致，将其同步即可，用新版本的替换老版本（反之也行）...
hive启动报错： Found class jline.Terminal, but interface was expected
weixin_30645617的博客
10-04 358
故障：[ERROR] Terminal initialization failed; falling back to unsupportedjava.lang.IncompatibleClassChangeError: Found class jline.Terminal, but interface was expected at jline.TerminalFactory.c...
hive 报错 Found class jline.Terminal, but interface was expected
wangwangliqing的博客
07-08 302
报错如下: java.lang.IncompatibleClassChangeError: Found class jline.Terminal, but interface was expected at jline.TerminalFactory.create(TerminalFactory.java:101) at jline.TerminalFactory....
HIve项目中常见错误，及修改办法
lz_N_one的博客
07-29 1285
HIve项目中常见错误，及修改办法
base/MasterData/oldWALs, maxLogs=10 2025-06-24 21:56:39,697 INFO [master/hadoop102:16000:becomeActiveMaster] wal.AbstractFSWAL: Closed WAL: AsyncFSWAL hadoop102%2C16000%2C1750773392926:(num 1750773399658) 2025-06-24 21:56:39,701 ERROR [master/hadoop102:16000:becomeActiveMaster] master.HMaster: Failed to become active master java.lang.IncompatibleClassChangeError: Found interface org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:615) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:610) at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:623) at org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:53) at org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:190) at org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:160) at org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:116) at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:719) at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:128) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:884) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:577) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:518) at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:160) at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62) at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:295) at org.apache.hadoop.hbase.master.region.MasterRegion.createWAL(MasterRegion.java:200) at org.apache.hadoop.hbase.master.region.MasterRegion.open(MasterRegion.java:263) at org.apache.hadoop.hbase.master.region.MasterRegion.create(MasterRegion.java:344) at org.apache.hadoop.hbase.master.region.MasterRegionFactory.create(MasterRegionFactory.java:104) at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:856) at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2199) at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:529) at java.lang.Thread.run(Thread.java:750) 2025-06-24 21:56:39,702 ERROR [master/hadoop102:16000:becomeActiveMaster] master.HMaster: ***** ABORTING master hadoop102,16000,1750773392926: Unhandled exception. Starting shutdown. ***** java.lang.IncompatibleClassChangeError: Found interface org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:615) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:610) at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:623) at org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:53) at org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:190) at org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:160) at org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:116) at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:719) at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:128) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:884) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:577) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:518) at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:160) at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62) at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:295) at org.apache.hadoop.hbase.master.region.MasterRegion.createWAL(MasterRegion.java:200) at org.apache.hadoop.hbase.master.region.MasterRegion.open(MasterRegion.java:263) at org.apache.hadoop.hbase.master.region.MasterRegion.create(MasterRegion.java:344) at org.apache.hadoop.hbase.master.region.MasterRegionFactory.create(MasterRegionFactory.java:104) at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:856) at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2199) at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:529) at java.lang.Thread.run(Thread.java:750) 2025-06-24 21:56:39,703 INFO [master/hadoop102:16000:becomeActiveMaster] regionserver.HRegionServer: ***** STOPPING region server 'hadoop102,16000,1750773392926' ***** 2025-06-24 21:56:39,703 INFO [master/hadoop102:16000:becomeActiveMaster] regionserver.HRegionServer: STOPPED: Stopped by master/hadoop102:16000:becomeActiveMaster 2025-06-24 21:56:40,607 INFO [master/hadoop102:16000] ipc.NettyRpcServer: Stopping server on /192.168.10.102:16000 2025-06-24 21:56:40,628 INFO [master/hadoop102:16000] regionserver.HRegionServer: Stopping infoServer 2025-06-24 21:56:40,652 INFO [master/hadoop102:16000] handler.ContextHandler: Stopped o.a.h.t.o.e.j.w.WebAppContext@45acdd11{master,/,null,STOPPED}{file:/opt/module/hbase-2.4.18/hbase-webapps/master} 2025-06-24 21:56:40,658 INFO [master/hadoop102:16000] server.AbstractConnector: Stopped ServerConnector@7efd28bd{HTTP/1.1, (http/1.1)}{0.0.0.0:16010} 2025-06-24 21:56:40,659 INFO [master/hadoop102:16000] server.session: node0 Stopped scavenging 2025-06-24 21:56:40,659 INFO [master/hadoop102:16000] handler.ContextHandler: Stopped o.a.h.t.o.e.j.s.ServletContextHandler@5f7da3d3{static,/static,file:///opt/module/hbase-2.4.18/hbase-webapps/static/,STOPPED} 2025-06-24 21:56:40,660 INFO [master/hadoop102:16000] handler.ContextHandler: Stopped o.a.h.t.o.e.j.s.ServletContextHandler@2b10ace9{logs,/logs,file:///opt/module/hbase-2.4.18/logs/,STOPPED} 2025-06-24 21:56:40,664 INFO [master/hadoop102:16000] regionserver.HRegionServer: aborting server hadoop102,16000,1750773392926 2025-06-24 21:56:40,665 INFO [master/hadoop102:16000] regionserver.HRegionServer: stopping server hadoop102,16000,1750773392926; all regions closed. 2025-06-24 21:56:40,665 INFO [master/hadoop102:16000] hbase.ChoreService: Chore service for: master/hadoop102:16000 had [] on shutdown 2025-06-24 21:56:40,672 WARN [master/hadoop102:16000] master.ActiveMasterManager: Failed get of master address: java.io.IOException: Can't get master address from ZooKeeper; znode data == null 2025-06-24 21:56:40,782 INFO [ReadOnlyZKClient-hadoop102:2181,hadoop103:2181,hadoop104:2181@0x1a9293ba] zookeeper.ZooKeeper: Session: 0x20000754c8c0002 closed 2025-06-24 21:56:40,782 INFO [ReadOnlyZKClient-hadoop102:2181,hadoop103:2181,hadoop104:2181@0x1a9293ba-EventThread] zookeeper.ClientCnxn: EventThread shut down for session: 0x20000754c8c0002 2025-06-24 21:56:40,797 INFO [master/hadoop102:16000] zookeeper.ZooKeeper: Session: 0x100007708c00000 closed 2025-06-24 21:56:40,797 INFO [main-EventThread] zookeeper.ClientCnxn: EventThread shut down for session: 0x100007708c00000 2025-06-24 21:56:40,797 INFO [master/hadoop102:16000] regionserver.HRegionServer: Exiting; stopping=hadoop102,16000,1750773392926; zookeeper connection closed. 2025-06-24 21:56:40,798 ERROR [main] master.HMasterCommandLine: Master exiting java.lang.RuntimeException: HMaster Aborted at org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:254) at org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:145) at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:82) at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:140) at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2969) [manager1@hadoop102 logs]$
最新发布
06-25
根据您提供的日志和引用内容，HMaster 异常终止的主要原因是 `java.lang.IncompatibleClassChangeError` 错误，特别是 `Found class jline.Terminal, but interface was expected`。这是典型的 JLine 库版本冲突问题...
Hive安装报错：Terminal initialization failed; falling back to unsupported
大数据技术杂谈
03-29 3566
[ERROR] Terminal initialization failed; falling back to unsupported java.lang.IncompatibleClassChangeError: Found class jline.Terminal, but interface was expected     at jline.TerminalFactory.cr
hive初次安装遇到的3个错误
DATA
04-08 1万+
首次安装hive，碰到一些问题，在此记录一下， 附：hive成功安装的记录：http://blog.csdn.net/bamuta/article/details/44940523 问题1：Unable to instantiate org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient [hadoop@hadoop
jline3, JLine是用于处理控制台输入的Java库.zip
10-09
jline3, JLine是用于处理控制台输入的Java库 描述JLine是用于处理控制台输入的Java库。 it functionality editline和 GNU 类似，但是具有额外的特性，使之与 ZSH行编辑器 par 。 熟悉 readline/editline功能的现代 shell
Hive报错：Found class jline.Terminal, but interface was expected
Devin
05-05 304
原因： hadoop目录下存在老版本jline-0.9.94.jar /$HADOOP_HOME/share/hadoop/yarn/lib： 解决： cp /hive/lib/jline-2.12.jar /$HADOOP_HOME/share/hadoop/yarn/lib
Hive启动报错： Found class jline.Terminal, but interface was expected
dengwan3818的博客
07-14 288
[ERROR] Terminal initialization failed; falling back to unsupported 2 java.lang.IncompatibleClassChangeError: Found class jline.Terminal, but interface was expected 3 at jline.T...
Hive：beeline启动Found class jline.Terminal, but interface was expected...
Joseph25的博客
04-02 227
Found class jline.Terminal, but interface was expected...
hive 启动报错 Found class jline.Terminal, but interface was expected
星月情缘的博客
01-08 489
             安装好hive后，准备启动。发现报错。 错误提示是这个:              Found class jline.Terminal, but interface was expected                   at jline.TerminalFactory.create(TerminalFactory.java:101)         at j...
java.lang.IncompatibleClassChangeError,Found class * but interface was expected
weixin_42242898的博客
05-25 611
1. java.lang.IncompatibleClassChangeError: Found class com.redis.RedisService, but interface was expected问题解析 2. javap 指令排查 3. java指令解析，invokestatic、invokevirtual、invokespecial、invokeinterface、invokedynamic
Hive启动Error：Found class jline.Terminal, but interface was expected
jvisualvm
04-14 311
Error  Cause —— Hadoop里面有老版本的jline   Solution cp jline-2.12.jar /home/hadoop/app/hadoop-2.6.4/share/hadoop/yarn/lib rm /home/hadoop/app/hadoop-2.6.4/share/hadoop/yarn/lib/jline-0.9.94.jar   重...
java.lang.IncompatibleClassChangeError: Found class com.*, but interface was expect
Theo9的博客
10-26 1677
java异常： Handler dispatch failed; nested exception is java.lang.IncompatibleClassChangeError: Found class com.*, but interface was expected 原因：版本不一致导致的冲突 修复：统一版本号
jline2报IncompatibleClassChangeError: Found class jline.Terminal, but interface was expected错误的解决方法
热门推荐
Laurence的技术博客
03-14 1万+
这个文章有点标题党的嫌疑了:)，但是我不会骗你，会给你一个解决方法，虽然不怎么好，但是至少可以解决你和我一样遇到的问题。情况是这样的：使用jline2,在windows下工作正常，linux下(redhat)报出：java.lang.IncompatibleClassChangeError: Found class jline.Terminal, but interface was expecte
dbeaver连接hive报错：sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException
03-11
### DBeaver 连接 Hive 安全证书验证错误解决方案 当遇到 `sun.security.validator.ValidatorException` 和 `PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException` 错误时，这通常意味着 Java 应用程序无法找到有效的认证路径来验证服务器的 SSL/TLS 证书。对于 DBeaver 连接到 Hive 的情况，可以采取以下措施： #### 修改 JVM 参数配置 为了使 DBeaver 能够信任特定的 CA 或自签名证书，在启动 DBeaver 之前设置环境变量或者修改其快捷方式中的目标字段，加入如下参数[^1]: ```bash -Djavax.net.ssl.trustStore=/path/to/trusted/cacerts.jks \ -Djavax.net.ssl.trustStorePassword=changeit ``` #### 导入所需证书到 cacerts 文件 如果问题是由于缺少某些根证书引起的，则可以通过导入这些缺失的证书至 JDK/JRE 自带的信任存储文件 (cacerts) 来解决问题。具体操作命令如下所示[^3]: ```bash keytool -importcert -file /path/to/your_certificate.cer \ -alias your_alias_name \ -keystore "$JAVA_HOME/jre/lib/security/cacerts" \ -storepass changeit ``` #### 配置 Maven 设置（适用于通过 Maven 构建项目） 如果是基于 Maven 开发的应用，并且遇到了类似的依赖项下载失败的情况，那么还需要确保本地计算机上的 Maven 已经被正确设置了全局级别的 trustStore 属性。 另外需要注意的是，有时可能是因为网络代理的原因导致 HTTPS 请求受阻而引发此类异常；此时应检查是否有合适的 HTTP(S)_PROXY 变量已定义并生效于当前运行环境中。 以上方法应该可以帮助解决大部分由 PKIX Path Building Failed 引起的问题。不过值得注意的是，安全性和合规性始终是最重要的考虑因素之一，因此建议仅限于开发测试环境下使用上述手段绕过严格的SSL握手流程。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值