Your message dated Mon, 23 Sep 2019 12:31:59 +0200 with message-id <[email protected]> and subject line This is a case of miss-configuration has caused the Debian Bug report #932813, regarding RabbitMQ init scripts are broken to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 932813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932813 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: rabbitmq-server Version: 3.7.8-4 Severity: minor Problem encountered while trying to update to debian-10. Steps to reproduce: 1. Uninstall rabbitmq with ‘apt-get remove rabbitmq-server’ 2. Install rabbitmq with ‘apt-get install rabbitmq-server’ Expected result: Rabbitmq is installed and immediately running via a systemd unit file and init script. Actual result: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libfile-copy-recursive-perl libjs-swfobject libjs-twitter-bootstrap libodbc1 tcpd Use 'apt autoremove' to remove them. The following NEW packages will be installed: rabbitmq-server 0 upgraded, 1 newly installed, 0 to remove and 359 not upgraded. Need to get 0 B/9,227 kB of archives. After this operation, 14.3 MB of additional disk space will be used. Selecting previously unselected package rabbitmq-server. (Reading database ... 105086 files and directories currently installed.) Preparing to unpack .../rabbitmq-server_3.7.8-4_all.deb ... Unpacking rabbitmq-server (3.7.8-4) ... Setting up rabbitmq-server (3.7.8-4) ... 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 "restart" failed. ● rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/rabbitmq-server.service.d └─limits.conf Active: activating (auto-restart) (Result: exit-code) since Tue 2019-07-23 17:04:53 CEST; 8ms ago Process: 31923 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, status=127) Process: 31921 ExecStart=/usr/sbin/rabbitmq-server (code=exited, status=127) Main PID: 31921 (code=exited, status=127) Jul 23 17:04:53 st05 systemd[1]: rabbitmq-server.service: Unit entered failed state. Jul 23 17:04:53 st05 systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'. dpkg: error processing package rabbitmq-server (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for systemd (232-25+deb9u11) ... Errors were encountered while processing: rabbitmq-server E: Sub-process /usr/bin/dpkg returned an error code (1) Something is broken in the init script. If you later attempt to start rabbitmq manually by running the executable indicated (/usr/sbin/rabbitmq-server) the program (so far) appears to run correctly. Running it via the system script later (systemctl start rabbitmq-server) produces the same error. There is no log output when rabbitmq fails this way. No startup log, No crash log, simply nothing, so the program is likely never ran.
--- End Message ---
--- Begin Message ---Hi, There's no issue in the package. In production, you should fix something like this in this file: NODE_IP_ADDRESS=10.0.0.2 NODE_PORT=5672 as you may wish to have rabbitmq listen on your cluster IP, but not potentially in a public IP address (typical use case in OpenStack, for example). So I don't think there's any issue in the package itself, therefore I'm closing the bug. If you happen to think otherwise, please let me know. Cheers, Thomas Goirand (zigo)
--- End Message ---
