Your message dated Thu, 2 Jun 2016 13:36:10 +0200 with message-id <[email protected]> and subject line Re: rabbitmqctl: Interrupting rabbitmqctl disrupts the terminal has caused the Debian Bug report #800647, regarding rabbitmqctl: Interrupting rabbitmqctl disrupts the terminal 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.) -- 800647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800647 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: rabbitmq-server Version: 3.5.4-1 Severity: normal File: /usr/lib/rabbitmq/bin/rabbitmq-script-wrapper Hi, Interrupting rabbitmqctl apparently causes a subprocess with a debugger to lurk in the background and eat characters indiscrimnately. root@data:~# rabbitmqctl cluster_status Cluster status of node rabbit@data ... ^C Session terminated, terminating shell... BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded (v)ersion (k)ill (D)b-tables (d)istribution ^C ...terminated. root@data:~# Eh? root@data:~# root@data:~# Eh? ^C root@data:~# ^C root@data:~# ^C root@data:~# ^C root@data:~# Process Information -------------------------------------------------- =proc:<0.38.0> State: Waiting Name: inet_gethost_native Spawned as: inet_gethost_native:server_init/2 Run queue: 1 Spawned by: <0.37.0> Started: Fri Oct 2 07:05:29 2015 Message queue length: 0 Number of heap fragments: 0 Heap fragment data: 0 Link list: [#Port<0.444>, <0.37.0>] Dictionary: [{rid,1},{num_requests,0}] Reductions: 83 Stack+heap: 233 OldHeap: 0 Heap unused: 17 OldHeap unused: 0 Memory: 2744 Stack dump: Program counter: 0x00007f54682a3708 (inet_gethost_native:main_loop/1 + 40) CP: 0x0000000000000000 (invalid) arity = 0 0x00007f54682d0900 Return addr 0x0000000000877d48 (<terminate process normally>) y(0) {state,#Port<0.444>,8000,12305,16402,<0.37.0>,4,{statistics,0,0,0,0,0,0,0,0}} (k)ill (n)ext (r)eturn: i^C root@data:~# [{nodes,[{disc,[rabbit@data,rabbit@store]},{ram,[rabbit@d2]}]}, {running_nodes,[rabbit@d2,rabbit@store,rabbit@data]}, {cluster_name,<<"rabbit@d2">>}, {partitions,[]}] root@data:~# -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (550, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rabbitmq-server depends on: ii adduser 3.113+nmu3 ii erlang-nox 1:18.0-dfsg-2 ii init-system-helpers 1.22 ii logrotate 3.8.7-1+b1 rabbitmq-server recommends no packages. rabbitmq-server suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Hi, Reading your log shows it looks like more a feature of rabbitmqctl than a bug (clearly, rabbitmqctl is catching the kill signal...). I'd suggest opening a bug upstream if you want this feature to change, as there's very little we can do at the Debian level. Cheers, Thomas Goirand (zigo)
--- End Message ---
