ubuntu 18.04中的Rabbitmq服务器安装错误

分类：编程问答

如何解决ubuntu 18.04中的Rabbitmq服务器安装错误

我正在尝试安装Rabbitmq。因此，我面临以下问题。对于安装，我正在使用此blog 

Reading package lists... Done
Building dependency tree       
Reading state information... Done
rabbitmq-server is already the newest version (3.8.7-1).
The following packages were automatically installed and are no longer required:
  erlang-diameter erlang-edoc erlang-erl-docgen erlang-eunit erlang-ic erlang-inviso erlang-nox erlang-odbc erlang-percept erlang-ssh libodbc1 libsctp1
Use 'sudo apt autoremove' to remove them.
0 upgraded,0 newly installed,0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation,0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up rabbitmq-server (3.8.7-1) ...
Job for rabbitmq-server.service failed because the control process exited with error code.
See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details.
invoke-rc.d: initscript rabbitmq-server,action "start" failed.
● rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2020-08-31 17:20:23 IST; 4ms ago
  Process: 6118 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited,status=1/FAILURE)
 Main PID: 6118 (code=exited,status=1/FAILURE)

Aug 31 17:20:23 mahesh-Latitude-3500 systemd[1]: Failed to start RabbitMQ broker.
dpkg: error processing package rabbitmq-server (--configure):
 installed rabbitmq-server package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 rabbitmq-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

很多次我都删除了所有Rabbitmq软件包并重新安装，但没有任何效果。

我尝试使用其他博客提供的以下命令解决此问题。

$ sudo apt-get update --fix-missing
$ sudo dpkg --configure -a
$ sudo apt-get install -f
$ sudo apt-get install rabbitmq-server -y --fix-missing

运行systemctl status rabbitmq-server.service

后的日志 
 rabbitmq-server.service - RabbitMQ broker
 Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
 Active: activating (auto-restart) (Result: exit-code) since Mon 2020-08-31 17:43:11 IST; 1s ago
 Process: 1878 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited,status=1/FAILURE)
 Main PID: 1878 (code=exited,status=1/FAILURE)

运行journalctl -xe

后记录 
-- Unit rabbitmq-server.service has begun starting up.
Aug 31 17:44:17 mahesh-Latitude-3500 rabbitmq-server[3761]: Configuring logger redirection
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   ##  ##      RabbitMQ 3.8.7
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   ##  ##
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   ##########  Copyright (c) 2007-2020 VMware,Inc. or its affiliates.
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   ######  ##
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   ##########  Licensed under the MPL 2.0. Website: https://rabbitmq.com
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   Doc guides: https://rabbitmq.com/documentation.html
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   Support:    https://rabbitmq.com/contact.html
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   Tutorials:  https://rabbitmq.com/getstarted.html
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   Monitoring: https://rabbitmq.com/monitoring.html
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   Logs: /var/log/rabbitmq/rabbit@mahesh-Latitude-3500.log
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:         /var/log/rabbitmq/rabbit@mahesh-Latitude-3500_upgrade.log
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   Config file(s): (none)
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]:   Starting broker...
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]: BOOT FAILED
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]: ===========
Aug 31 17:44:19 mahesh-Latitude-3500 rabbitmq-server[3761]: Error during startup: {error,{could_not_start_listener,"::",5672,eaddrinuse}}
Aug 31 17:44:20 mahesh-Latitude-3500 rabbitmq-server[3761]: {"init terminating in do_boot",{error,eaddrinuse}}}
Aug 31 17:44:20 mahesh-Latitude-3500 rabbitmq-server[3761]: init terminating in do_boot ({error,::,eaddrinuse}})
Aug 31 17:44:20 mahesh-Latitude-3500 rabbitmq-server[3761]: [1B blob data]
Aug 31 17:44:20 mahesh-Latitude-3500 rabbitmq-server[3761]: Crash dump is being written to: /var/log/rabbitmq/erl_crash.dump...done
Aug 31 17:44:20 mahesh-Latitude-3500 systemd[1]: rabbitmq-server.service: Main process exited,code=exited,status=1/FAILURE
Aug 31 17:44:20 mahesh-Latitude-3500 systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'.
Aug 31 17:44:20 mahesh-Latitude-3500 systemd[1]: Failed to start RabbitMQ broker.
-- Subject: Unit rabbitmq-server.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit rabbitmq-server.service has failed.
-- 
-- The result is RESULT.
Aug 31 17:44:30 mahesh-Latitude-3500 systemd[1]: rabbitmq-server.service: Service hold-off time over,scheduling restart.
Aug 31 17:44:30 mahesh-Latitude-3500 systemd[1]: rabbitmq-server.service: Scheduled restart job,restart counter is at 179.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Automatic restarting of the unit rabbitmq-server.service has been scheduled,as the result for
-- the configured Restart= setting for the unit.
Aug 31 17:44:30 mahesh-Latitude-3500 systemd[1]: Stopped RabbitMQ broker.
-- Subject: Unit rabbitmq-server.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit rabbitmq-server.service has finished shutting down.
Aug 31 17:44:30 mahesh-Latitude-3500 systemd[1]: Starting RabbitMQ broker...
-- Subject: Unit rabbitmq-server.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit rabbitmq-server.service has begun starting up.

没有任何效果。请帮忙。

谢谢。

解决方法

问题很可能是rabbitmq 尝试使用的端口当前正被另一个进程使用。 这在 journalctl -xe

的输出中说明 
... : Error during startup: {error,{could_not_start_listener,"::",5672,eaddrinuse}}

您可以使用

查看机器上当前正在使用的所有端口 
$ lsof -i -P -n

或专门检查该端口

$ lsof -i -P -n|grep 5672

因此您可以使用端口 5672 终止进程或更改 rabbitmq 使用的端口

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 dio@foxmail.com 举报，一经查实，本站将立刻删除。

相关推荐

导入项目后报错问题
依赖报错 idea导入项目后依赖报错，解决方案：https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错：更换其他版本 无法下载依赖可参考：https://blog.csdn.net/weixin_42628809/a
idea不能识别yaml文件
使用mybatis plus常见错误
错误1：代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
gradle常见问题与错误
错误1：gradle项目控制台输出为乱码 # 解决方案：https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
Mybatis Plus传入参数0不起作用
错误还原：在查询的过程中，传入的workType为0时，该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
linux中make编译源码包失败
报错如下，gcc版本太低 ^ server.c:5346:31: 错误：‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
微服务启动错误：Command line is too long. Shorten command line for
解决方案1 1、改项目中.idea/workspace.xml配置文件，增加dynamic.classpath参数 2、搜索PropertiesComponent，添加如下 <property name="dynamic.classpath" value="tru
vue常见错误
删除根组件app.vue中的默认代码后报错：Module Error (from ./node_modules/eslint-loader/index.js): 解决方案：关闭ESlint代码检测，在项目根目录创建vue.config.js，在文件中添加 module.exports = { lin
spark常见错误
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
matplotlib报错：AttributeError: module 'backend_interagg' has no attribute 'FigureCanvas'. Did you mean: 'FigureCanvasAgg'?
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
gitlab登录失败，报错：This challenge page was accidentally cached by an intermediary and is no longer available.
设置时间 控制面板
后端开发常见错误
错误1：Request method ‘DELETE‘ not supported 错误还原：controller层有一个接口，访问该接口时报错：Request method ‘DELETE‘ not supported 错误原因：没有接收到前端传入的参数，修改为如下 参考 错误2：cannot r
docker常见错误
错误1：启动docker镜像时报错：Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法：重启docker -> systemctl r
idea常见错误
错误1：private field ‘xxx‘ is never assigned 按Altʾnter快捷键，选择第2项 参考：https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2：启动时报错，不能找到主启动类 #
pip安装依赖失败
报错如下，通过源不能下载，最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
maven常见错误
错误1：maven打包报错 错误还原：使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
cloud项目中常见错误
错误1：服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
springboot常见错误
错误1：运行项目后报如下错误 解决方案 报错2：Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案：在pom.
springmvc拦截器中使用redisTemplate报空指针异常
参考 错误原因 过滤器或拦截器在生效时，redisTemplate还没有注入 解决方案：在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
vite报错：npm ERR! command C:WINDOWSsystem32cmd.exe /d /s /c C:UsersychenAppDataLocalTempnpx-dde1c848.cmd
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-
pythonJavaScriptjavaHTMLPHPreactjsC#AndroidCSSNode.jssqlrpython-3.xMysqLjQueryc++pandasFlutterangularIOSdjangolinuxswifttypescript路由器JSON路由器设置无线路由器h3c华三华三路由器设置华三路由器电脑软件教程arraysdocker软件图文教程Cvue.jslaravelspring-boot