关于提示SLF4J: Class path contains multiple SLF4J bindings的问题解决

2023-11-26 19:04

本文主要是介绍关于提示SLF4J: Class path contains multiple SLF4J bindings的问题解决,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

 


         今天搭建hbase的时候启动hbase的时候shell面板输入了一大堆日志,如下:

stopping hbase.....................
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
[atguigu@hadoop102 software]$ start-hbase.sh 
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
running master, logging to /opt/software/hbase/logs/hbase-atguigu-master-hadoop102.out
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
192.168.10.102: running regionserver, logging to /opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop102.out
hadoop104: mv: 无法获取"/opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop104.out.4" 的文件状态(stat): 没有那个文件或目录
192.168.10.104: mv: 无法获取"/opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop104.out.3" 的文件状态(stat): 没有那个文件或目录
192.168.10.104: mv: 无法获取"/opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop104.out.2" 的文件状态(stat): 没有那个文件或目录
192.168.10.104: mv: 无法获取"/opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop104.out.1" 的文件状态(stat): 没有那个文件或目录
hadoop104: running regionserver, logging to /opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop104.out
192.168.10.104: running regionserver, logging to /opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop104.out
192.168.10.104: mv: 无法获取"/opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop104.out" 的文件状态(stat): 没有那个文件或目录
hadoop102: running regionserver, logging to /opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop102.out
192.168.10.103: mv: 无法获取"/opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop103.out.4" 的文件状态(stat): 没有那个文件或目录
192.168.10.103: mv: 无法获取"/opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop103.out.3" 的文件状态(stat): 没有那个文件或目录
192.168.10.103: mv: 无法获取"/opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop103.out.2" 的文件状态(stat): 没有那个文件或目录
192.168.10.103: mv: 无法获取"/opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop103.out.1" 的文件状态(stat): 没有那个文件或目录
hadoop103: running regionserver, logging to /opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop103.out
192.168.10.103: running regionserver, logging to /opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop103.out
192.168.10.103: mv: 无法获取"/opt/software/hbase/logs/hbase-atguigu-regionserver-hadoop103.out" 的文件状态(stat): 没有那个文件或目录
192.168.10.104: SLF4J: Class path contains multiple SLF4J bindings.
192.168.10.104: SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
192.168.10.104: SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
192.168.10.104: SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
192.168.10.104: SLF4J: Class path contains multiple SLF4J bindings.
192.168.10.104: SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
192.168.10.104: SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
192.168.10.104: SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
192.168.10.104: SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
192.168.10.104: SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
hadoop104: SLF4J: Class path contains multiple SLF4J bindings.
hadoop104: SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
hadoop104: SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
hadoop104: SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
hadoop104: SLF4J: Class path contains multiple SLF4J bindings.
hadoop104: SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
hadoop104: SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
hadoop104: SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
hadoop104: SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
hadoop104: SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
192.168.10.103: SLF4J: Class path contains multiple SLF4J bindings.
192.168.10.103: SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
192.168.10.103: SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
192.168.10.103: SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
192.168.10.103: SLF4J: Class path contains multiple SLF4J bindings.
192.168.10.103: SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
192.168.10.103: SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
192.168.10.103: SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
192.168.10.103: SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
192.168.10.103: SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
hadoop103: SLF4J: Class path contains multiple SLF4J bindings.
hadoop103: SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
hadoop103: SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
hadoop103: SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
hadoop103: SLF4J: Class path contains multiple SLF4J bindings.
hadoop103: SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
hadoop103: SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
hadoop103: SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
hadoop103: SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
hadoop103: SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
 

        划重点:SLF4J: Class path contains multiple SLF4J bindings(  类路径包含多个绑定的意思)

        SLF4J: Found binding in [jar:file:/opt/software/hadoop-3.1.3/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/opt/software/hbase/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]

        这上面输入了三台节点hadoop的slf4j-log4j12-1.7.25.jar的jar包和hbase的slf4j-log4j12-1.7.25.jar的jar包版本都一样所以不是兼容性问题,所以是类路径包含多个SLF4J绑定。

        解决方法:

        在hbase的hbase-env.sh文件中进行修改(如果有这一行的话就把注释去掉,是其配置生效)或者增加(如果没有这一行配置,就增加到文件中)。

HBASE_DISABLE_HADOOP_CLASSPATH_LOOKUP=true 

        修改完成之后,重启hbase

        现在就简单清爽的很快了!当然非强迫患者,这个也可以不修改,不过对以后日志输出增加巨大的冗余。


        


感谢各位的观看,创作不易,能不能给哥们来一个点赞呢!!!

好了,今天的分享就这么多了,有什么不清楚或者我写错的地方,请多多指教!

私信,评论我呗!!!!!!

关注我下一篇不迷路哦!

 

这篇关于关于提示SLF4J: Class path contains multiple SLF4J bindings的问题解决的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/426183

相关文章

Vue3绑定props默认值问题

《Vue3绑定props默认值问题》使用Vue3的defineProps配合TypeScript的interface定义props类型,并通过withDefaults设置默认值,使组件能安全访问传入的... 目录前言步骤步骤1:使用 defineProps 定义 Props步骤2:设置默认值总结前言使用T

504 Gateway Timeout网关超时的根源及完美解决方法

《504GatewayTimeout网关超时的根源及完美解决方法》在日常开发和运维过程中,504GatewayTimeout错误是常见的网络问题之一,尤其是在使用反向代理(如Nginx)或... 目录引言为什么会出现 504 错误?1. 探索 504 Gateway Timeout 错误的根源 1.1 后端

Web服务器-Nginx-高并发问题

《Web服务器-Nginx-高并发问题》Nginx通过事件驱动、I/O多路复用和异步非阻塞技术高效处理高并发,结合动静分离和限流策略,提升性能与稳定性... 目录前言一、架构1. 原生多进程架构2. 事件驱动模型3. IO多路复用4. 异步非阻塞 I/O5. Nginx高并发配置实战二、动静分离1. 职责2

解决升级JDK报错:module java.base does not“opens java.lang.reflect“to unnamed module问题

《解决升级JDK报错:modulejava.basedoesnot“opensjava.lang.reflect“tounnamedmodule问题》SpringBoot启动错误源于Jav... 目录问题描述原因分析解决方案总结问题描述启动sprintboot时报以下错误原因分析编程异js常是由Ja

深度剖析SpringBoot日志性能提升的原因与解决

《深度剖析SpringBoot日志性能提升的原因与解决》日志记录本该是辅助工具,却为何成了性能瓶颈,SpringBoot如何用代码彻底破解日志导致的高延迟问题,感兴趣的小伙伴可以跟随小编一起学习一下... 目录前言第一章:日志性能陷阱的底层原理1.1 日志级别的“双刃剑”效应1.2 同步日志的“吞吐量杀手”

MySQL 表空却 ibd 文件过大的问题及解决方法

《MySQL表空却ibd文件过大的问题及解决方法》本文给大家介绍MySQL表空却ibd文件过大的问题及解决方法,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考... 目录一、问题背景:表空却 “吃满” 磁盘的怪事二、问题复现:一步步编程还原异常场景1. 准备测试源表与数据

解决Nginx启动报错Job for nginx.service failed because the control process exited with error code问题

《解决Nginx启动报错Jobfornginx.servicefailedbecausethecontrolprocessexitedwitherrorcode问题》Nginx启... 目录一、报错如下二、解决原因三、解决方式总结一、报错如下Job for nginx.service failed bec

SysMain服务可以关吗? 解决SysMain服务导致的高CPU使用率问题

《SysMain服务可以关吗?解决SysMain服务导致的高CPU使用率问题》SysMain服务是超级预读取,该服务会记录您打开应用程序的模式,并预先将它们加载到内存中以节省时间,但它可能占用大量... 在使用电脑的过程中,CPU使用率居高不下是许多用户都遇到过的问题,其中名为SysMain的服务往往是罪魁

MySQ中出现幻读问题的解决过程

《MySQ中出现幻读问题的解决过程》文章解析MySQLInnoDB通过MVCC与间隙锁机制在可重复读隔离级别下解决幻读,确保事务一致性,同时指出性能影响及乐观锁等替代方案,帮助开发者优化数据库应用... 目录一、幻读的准确定义与核心特征幻读 vs 不可重复读二、mysql隔离级别深度解析各隔离级别的实现差异

C++ vector越界问题的完整解决方案

《C++vector越界问题的完整解决方案》在C++开发中,std::vector作为最常用的动态数组容器,其便捷性与性能优势使其成为处理可变长度数据的首选,然而,数组越界访问始终是威胁程序稳定性的... 目录引言一、vector越界的底层原理与危害1.1 越界访问的本质原因1.2 越界访问的实际危害二、基