Package: rabbitmq-server Version: 3.7.8-4 Severity: important # rabbitmqctl list_unresponsive_queues Listing unresponsive queues for vhost / ... ^C Session terminated, killing shell... ...killed. #
Unfortunately, contrary to this message, the Erlang shell is NOT killed; it lingers in the background and reads whatever input characters it can grab. Thus my shell is now basically unuseable unless I log in on a second terminal, find the beam.smp process in question (it's re-parented to PID 1), and kill it off. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (700, 'stable'), (600, 'unstable'), (550, 'experimental'), (550, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rabbitmq-server depends on: ii adduser 3.118 pn erlang-base | erlang-base-hipe <none> pn erlang-crypto <none> pn erlang-eldap <none> pn erlang-inets <none> pn erlang-mnesia <none> pn erlang-nox | esl-erlang <none> pn erlang-os-mon <none> pn erlang-parsetools <none> pn erlang-public-key <none> pn erlang-runtime-tools <none> pn erlang-ssl <none> pn erlang-syntax-tools <none> pn erlang-tools <none> pn erlang-xmerl <none> ii init-system-helpers 1.56+nmu1 pn locales-all <none> pn logrotate <none> ii lsb-base 10.2019051400 ii python 2.7.16-1 pn socat <none> rabbitmq-server recommends no packages. rabbitmq-server suggests no packages.
