Rocketmq创建topic报错org.apache.rocketmq.acl.common.AclException: [10015:signature-failed] unable to cal

已于 2022-07-25 18:14:09 修改
阅读量4.6k 收藏 3
点赞数 3
分类专栏： # RocketMQ 文章标签： linux
于 2020-07-15 14:24:07 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/tootsy_you/article/details/107359772
版权 
[root@localhost bin] ./mqadmin updateTopic -b localhost:10911  -t aaa
RocketMQLog:WARN No appenders could be found for logger (io.netty.util.internal.PlatformDependent0).
RocketMQLog:WARN Please initialize the logger system properly.
org.apache.rocketmq.tools.command.SubCommandException: UpdateTopicSubCommand command failed
	at org.apache.rocketmq.tools.command.topic.UpdateTopicSubCommand.execute(UpdateTopicSubCommand.java:185)
	at org.apache.rocketmq.tools.command.MQAdminStartup.main0(MQAdminStartup.java:139)
	at org.apache.rocketmq.tools.command.MQAdminStartup.main(MQAdminStartup.java:90)
Caused by: org.apache.rocketmq.acl.common.AclException: [10015:signature-failed] unable to calculate a request signature. error=[10015:signature-failed] unable to calculate a request signature. error=Algorithm HmacSHA1 not available
	at org.apache.rocketmq.acl.common.AclSigner.signAndBase64Encode(AclSigner.java:84)
	at org.apache.rocketmq.acl.common.AclSigner.calSignature(AclSigner.java:73)
	at org.apache.rocketmq.acl.common.AclSigner.calSignature(AclSigner.java:68)
	at org.apache.rocketmq.acl.common.AclUtils.calSignature(AclUtils.java:69)
	at org.apache.rocketmq.acl.common.AclClientRPCHook.doBeforeRequest(AclClientRPCHook.java:44)
	at org.apache.rocketmq.remoting.netty.NettyRemotingAbstract.doBeforeRpcHooks(NettyRemotingAbstract.java:172)
	at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:368)
	at org.apache.rocketmq.client.impl.MQClientAPIImpl.createTopic(MQClientAPIImpl.java:284)
	at org.apache.rocketmq.tools.admin.DefaultMQAdminExtImpl.createAndUpdateTopicConfig(DefaultMQAdminExtImpl.java:182)
	at org.apache.rocketmq.tools.admin.DefaultMQAdminExt.createAndUpdateTopicConfig(DefaultMQAdminExt.java:163)
	at org.apache.rocketmq.tools.command.topic.UpdateTopicSubCommand.execute(UpdateTopicSubCommand.java:139)
	... 2 more
Caused by: org.apache.rocketmq.acl.common.AclException: [10015:signature-failed] unable to calculate a request signature. error=Algorithm HmacSHA1 not available
	at org.apache.rocketmq.acl.common.AclSigner.sign(AclSigner.java:63)
	at org.apache.rocketmq.acl.common.AclSigner.signAndBase64Encode(AclSigner.java:79)
	... 12 more
Caused by: java.security.NoSuchAlgorithmException: Algorithm HmacSHA1 not available
	at javax.crypto.Mac.getInstance(Mac.java:181)
	at org.apache.rocketmq.acl.common.AclSigner.sign(AclSigner.java:57)
	... 13 more

错误原因:jar包引用失败
解决办法
在tool.sh 中${JAVA_HOME}/jre/lib/ext后加上ext文件夹的绝对路径（jdk路径）

 vim /app/rocketmq/bin/tools.sh
 如JAVA_OPT="${JAVA_OPT} -Djava.ext.dirs=${BASE_DIR}/lib:${JAVA_HOME}/jre/lib/ext:${JAVA_HOME}/lib/ext:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.x86_64/jre/lib/ext"

在这里插入图片描述

早九晚十二
关注
  • 3
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 1
    评论
专栏目录
Cyber.Forensics.eBook-EEn.pdf.7z
08-21
Introduction As an auditor as well as researcher and author, I realize and value the importance of timely, well−focused, accurate information. It is with this philosophy in mind that the development of this project was undertaken. To the reader, a note of explanation…. This is not a text, but rather a field manual. It has been written — better yet, compiled — and edited in a manner that will allow you to rapidly access a specific area of interest or concern and not be forced to sequentially wade through an entire text, chapter by chapter, to get to what is important to you. In the true sense of a field manual, each "chapter" (and we use that term loosely) stands on its own and presents focused, timely information on a specific topic related to cyber forensics. The author of each "chapter" was selected for his or her expertise in a specific area within the very broad field of cyber forensics. Often a limiting aspect of most projects, especially those written on emerging technical topics, is the inability to cover every aspect of the topic in a single all−inclusive text. This truth befalls this field manual that you are about to use. Initial research into this growing discipline proved that it would be next to impossible to include all the areas of both interest and importance in the field of cyber forensics that would be needed and required by all potential readers and users in a single text. Thus, this field manual presents specific and selected topics in the discipline of cyber forensics, and addresses critical issues facing the reader who is engaged in or who soon will be (and you will!) engaged in the preservation, identification, extraction, and documentation of computer evidence. As a user of this field manual, you will see that this manual's strength lies with the inclusion of an exhaustive set of chapters covering a broad variety of forensic subjects. Each chapter was thoroughly investigated; examined for accuracy, completeness, and appropriateness to the study of cyber forensics; reviewed by peers; and then compiled in a comprehensive, concise format to present critical topics of interest to professionals working in the growing field of cyber forensics. We finally had to select several key areas and put pen to paper, entice several colleagues to share their ideas, and resign ourselves to the fact that we cannot say all that needs to be said in one text, book, or manual. We trust the material we have included will serve as a starting point for the many professionals who are beginning their journey into this exciting discipline. We begin our journey into the realm of this relatively new discipline by opening with a brief discussion as to the current state of the environment relating to the need for this new field of forensics and then a brief examination of the origins of cyber forensics. Along the way, we will establish several basic definitions designed to assist the reader in moving easily through what could be difficult and confusing terrain. Although e−mail is becoming more mission−critical for enterprises, it also has the ability to haunt a company in times of trouble, because records of e−mail messages remain in the company systems after deletion — a feature highlighted during the Microsoft anti−trust trial. The case has featured critical testimony derived from old Microsoft e−mail messages.
rocketmq-console-ng-1.0.1.jar
08-15
RocketMQ-Console是RocketMQ项目的扩展插件，是一个图形化管理控制台，提供Broker集群状态查看，Topic管理，Producer、Consumer状态展示，消息查询等常用功能，这个功能在安装好RocketMQ后需要额外单独安装、运行。 使用方式：上传至linux服务器后，以jar包方式运行 -jar包运行 java -jar rocketmq-console-ng-1.0.1.jar --server.port=9999 --rocketmq.config.namesrvAddr=192.168.207.128:9876;192.168.207.129:9876 (ip替换为RocketMQ集群节点ip)
rocketmq-all-4.7.1-bin-release.zip
09-03
RocketMQ主要由 Producer、Broker、Consumer 三部分组成，其中Producer 负责生产消息，Consumer 负责消费消息，Broker 负责存储消息。Broker 在实际部署过程中对应一台服务器，每个 Broker 可以存储多个Topic的消息，每个Topic的消息也可以分片存储于不同的 Broker。Message Queue 用于存储消息的物理地址，每个Topic中的消息地址存储于多个 Message Queue 中。ConsumerGroup 由多个Consumer 实例构成。
rocketmq-console.zip
03-10
RocketMQ-Console是RocketMQ项目的扩展插件，是一个图形化管理控制台，提供Broker集群状态查看，Topic管理，Producer、Consumer状态展示，消息查询等常用功能，这个功能在安装好RocketMQ后需要额外单独安装、运行。
RocketMQ ACL版本升级过程中的曲折经历(大厂线上环境大规模MQ升级开启ACL实战)
中间件兴趣圈
05-09 1642
RocketMQ是一款非常优秀的主流中间件，本文是RocketMQ系列的第52篇文章，重点阐述笔者在公司升级RocketMQ集群并开启ACL的真实经历，并且遇到的一些问题及其解决方案，实战性非常强。 1、ACL机制的重要性 某一天突然接到安全团队的通知，公司内网部署的RocketMQ集群安全性非常低，需要立马整改。 接到安全团队的通知，马上开启了复盘，公司内部的RocketMQ集群还是基于RocketMQ4.1搭建的，存在重大安全隐患，因为生产环境的任意一台机器，不需要知道RocketMQ集群所在机器的密码
【消息队列】RocketMQ 使用过程中遇到的问题
技术能量站
01-11 2813
一、问题汇总 （1）service not available now, maybe disk full, CL: 1.00 CQ: 1.00 INDEX: 1.00, maybe your broker machine memory too small 问题原因：该报错由于 /store/commitlog文件夹下的日志文件过大造成 df -h 指令查看当前磁盘占用内存情况 rocketmq默认会把剩余磁盘的比率不足75% 当做磁盘空间不足处理 解决办法： 先删除掉/st...
RocketMQ开启ACL后客户端连接报Algorithm HmacSHA1 not available的解决方式
Aubrey.J的博客
07-11 2310
RocketMQ开启ACL后，客户端、Dashboard连接报Algorithm HmacSHA1 not available错误，异常日志如下 unable to calculate a request signature. error=[10015:signature-failed] unable to calculate a request signature. error=Algorithm HmacSHA1 not available, org.apache.rocket...
虚拟机中linux中用rocketMQ发布updateTopic发生unable to calculate a request signature. error=Algorithm HmacSHA1
fuqinglinbin的博客
07-26 1797
[root@localhost bin]# ./mqadmin updateTopic -n localhost:9876 -t stock -c DefaultCluster OpenJDK 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 OpenJDK 64-Bit Serv...
rocket无法创建topic，报异常AclException: [10015:signature-failed] unable to calculate a request signatu
a2868221132的博客
06-23 2366
1.查询ext文件 find / -name 'ext' |grep jdk 结果：/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64/jre/lib/ext 2.进入rocket下的bin目录，执行： vi tools.sh 修改前： #=========================================================================================== # JVM C
RocketMQ常见错误与解决方案
我引源,你思考
07-21 3630
1. 通过rocketmq-console查询Topic是否存在2. 查看配置文件, Broker是否开启了自动创建Topic，参数为：autoCreateTopicEnable, 该参数默认为true,但在生产环境不建议开启。3. 如果开启了自动创建Topic，但还是抛出这个错误，这个时候请检查客户端(Producer)连接的Nameserver地址是否与Broker中配置的nameserver地址是否一致。RocketMQ每一分钟打印前一分钟内消息发送的耗时情况分布。
RocketMQ实战异常汇总
热门推荐
小萝卜.的博客
07-16 1万+
今天的博客主题 MQ消息中间件 --》RocketMQ --》RocketMQ实战异常汇总 目录 No route info of this topic, xxxTopic CODE: 1 DESC: The broker does not support consumer to filter message by SQL92 MQ控制台查询%DLQ%Topic消息异常 b...
详解RocketMQ ACL机制的设计实现原理
HackDaily
04-24 725
从配置使用、实现思路、匹配和校验、源码分析等角度出发，解读RocketMQ ACL机制的设计和实现原理，最后还给出了使用过程中的踩坑经验分享
十一、springCloud之stream
RT_0114的博客
09-07 178
springCloud之stream
docker-compose 部署rocketMq后创建topic出错
feichen2016的博客
09-03 1153
发送消息时出现错误 MQClientException: No route info of this topic, TopicTest 进入docker容器，docker exec -it rmqnamesrv /bin/sh 查看具体日志：mqadmin topicRoute -n localhost:9876 -t TopicTest org.apache.rocketmq.tools.command.SubCommandException: TopicRouteSubCommand comma
rocketMQ报错：No accessKey is configured
黎明小书生
11-12 6718
错误： CODE: 1 DESC: org.apache.rocketmq.acl.common.AclException: No accessKey is configured 在broker中配置aclEnable=true之后，消费者生产者可以正常工作！启动rocketmq-console报错！ 大概报错信息如下： java.lang.RuntimeException: org.apache.rocketmq.client.exception.MQBrokerException: CODE: 1 D
源码分析RocketMQ ACL实现机制
中间件兴趣圈
07-07 3042
有关RocketMQ ACL的使用请查看上一篇《RocketMQ ACL使用指南》，本文从源码的角度，分析一下RocketMQ ACL的实现原理。 备注：RocketMQ在4.4.0时引入了ACL机制，本文代码基于RocketMQ4.5.0版本。 本节目录1、BrokerController#initialAcl2、PlainAccessValidator2.1 类图2.1.2 PlainAc...
rocketMQ：unable to calculate a request signature. error=Algorithm HmacSHA1 not available
我不是李大侠
07-10 6714
rocketMQ使用 ./mqadmin topicList -n localhost:9876报错 org.apache.rocketmq.tools.command.SubCommandException: TopicListSubCommand command failed at org.apache.rocketmq.tools.command.topic.TopicListSubCom...
RocketMQ发布编写ACL性能测试脚本报错unable to calculate a request signature. error=Algorithm HmacSHA1
qq_34158117的博客
08-20 2561
RocketMQ发布编写性能测试脚本报错unable to calculate a request signature. error=Algorithm HmacSHA1 RocketMQ版本4.5.2 /* * Licensed to the Apache Software Foundation (ASF) under one or more * contributor li...
spring cloud eureka搭建报错<init>
chenzhouwa4173的博客
06-27 216
11:47:19.523 [main] ERROR org.springframework.boot.SpringApplication - Application run failed java.lang.NoSuchMethodError: org.springframework.boot...
rocketmq创建topic报错Caused by: org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to 192.168.0.3:9877 failed
最新发布
10-09
对于该错误，通常是由于连接到指定的 RocketMQ broker 失败引起的。可能的原因包括： 1. Broker 未启动或未正常运行。 2. Broker 的 IP 地址或端口号配置错误。 3. 防火墙或网络配置导致无法连接到指定的地址和端口。 您可以按照以下步骤来解决该问题： 1. 确保 RocketMQ broker 已经正确启动并正在运行。 2. 检查您在创建 topic 时指定的 broker 的 IP 地址和端口号是否正确。 3. 检查防火墙或网络配置，确保可以连接到指定的 broker 地址和端口。 如果问题仍然存在，请尝试使用其他网络环境或联系您的系统管理员以获取更多帮助。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

早九晚十二

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值