package rabbitmq-server 3.9.13-1 failed to install/upgrade: installed rabbitmq-server package post-installation script subprocess returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rabbitmq-server (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
not working after updating from 20 to 22 lts
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: rabbitmq-server 3.9.13-1
ProcVersionSign
Uname: Linux 5.14.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckR
Date: Fri Apr 22 12:01:33 2022
ErrorMessage: installed rabbitmq-server package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-11-25 (148 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitec
Python3Details: /usr/bin/
PythonDetails: N/A
RelatedPackageV
dpkg 1.21.1ubuntu2
apt 2.4.5
SourcePackage: rabbitmq-server
Title: package rabbitmq-server 3.9.13-1 failed to install/upgrade: installed rabbitmq-server package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile.
tags: | removed: need-duplicate-check |
Thanks for taking the time to file this bug and trying to make Ubuntu better.
The attached logs are not that helpful to understand what is happening. I did set up a Focal container and installed rabbitmq-server, also changed the default config to match yours (setting "ulimit -n 1024"), after that I did run do-release-upgrade to move to Jammy. The upgrade went fine and by the end of the process rabbitmq-server systemd service was still active and running. Not sure what exactly happened in your system to get this failure. Could you please try to provided any detailed steps to reproduce this issue? Otherwise we cannot act on it.
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".
For local configuration issues, you can find assistance here: www.ubuntu. com/support/ community
http://