MySQL Bugs: #72873: mysqlfabric raises exception when run 'mysqlfabric manage stop'

Bug #72873	mysqlfabric raises exception when run 'mysqlfabric manage stop'
Submitted:	4 Jun 2014 12:23	Modified:	9 Jun 2014 13:14
Reporter:	Shahriyar Rzayev	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Fabric	Severity:	S4 (Feature request)
Version:	1.4.3	OS:	Linux (CentOS 6.5)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
After starting mysqlfabric:
[root@fabricsrv log]# mysqlfabric manage start

From Another terminal run:
[root@fabricsrv log]# mysqlfabric manage stop

And from terminal which we run start we will see Python exception.

[DEBUG] 1401884186.115608 - XML-RPC-Session-3 - Finishing request (<socket._socketobject object at 0x21e9f30>) from (('127.0.0.1', 42621)) through thread (<SessionThread(XML-RPC-Session-3, started daemon 140136832550656)>).
Exception in thread XML-RPC-Session-3 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
  File "/usr/lib/python2.6/site-packages/mysql/fabric/protocols/xmlrpc.py", line 581, in run
  File "/usr/lib/python2.6/site-packages/mysql/fabric/protocols/xmlrpc.py", line 359, in register_thread
  File "/usr/lib64/python2.6/Queue.py", line 138, in put
  File "/usr/lib64/python2.6/threading.py", line 274, in notify
<type 'exceptions.TypeError'>: 'NoneType' object is not callable
Exception in thread Thread-17 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
  File "/usr/lib64/python2.6/threading.py", line 734, in run
  File "/usr/lib64/python2.6/threading.py", line 395, in wait
  File "/usr/lib64/python2.6/threading.py", line 263, in wait
<type 'exceptions.ValueError'>: list.remove(x): x not in list

How to repeat:
Run from terminal n1 -> mysqlfabric manage start
Run from terminal n2 -> mysqlfabric manage stop to see exception.

Suggested fix:
No idea.

Hi Shashryiar!

Thank you for the bug report. The printout is an exception occurring in the server that is shown by the client, but it does not mean that the server fails to stop.

After you have issued the "mysqlfabric manage stop" command, is the server still running?

[DEBUG] 1402300262.031930 - XML-RPC-Session-2 - Finishing request (<socket._socketobject object at 0x1d4c130>) from (('127.0.0.1', 39038)) through thread (<SessionThread(XML-RPC-Session-2, started daemon 140626670638848)>).

Bye.
Exception in thread XML-RPC-Session-2 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
  File "/usr/lib/python2.6/site-packages/mysql/fabric/protocols/xmlrpc.py", line 581, in run
  File "/usr/lib/python2.6/site-packages/mysql/fabric/protocols/xmlrpc.py", line 359, in register_thread
  File "/usr/lib64/python2.6/Queue.py", line 138, in put
  File "/usr/lib64/python2.6/threading.py", line 274, in notify
<type 'exceptions.TypeError'>: 'NoneType' object is not callable

[root@fabricsrv ~]# mysqlfabric manage ping
[Errno 111] Connection refused

Connection refused? It seems that fabric is stopped. But connection refused is not an informative message. We have seen this error mainly because of firewall configuration or something else but when something is stopped.

Thank you Shahriyar,

Since the Fabric node have stopped, this is just an uninformative error message and not a bug that "Represents a complete loss of service, a significant functionality is missing, a system that hangs indefinitely; and there is no available workaround."

Since this is mostly about an uninformative error message and an exception that is raised, this should be considered a severity 4 bug ("There is no loss in service; a cosmetic or enhancement request.").

We do, however, prioritize bugs that make the system hard to use due to unhelpful error messages so we will will prioritize it accordingly.

Thank you for the bug report, verified as described.

Status updated to 'Won't fix' (Fabric is now covered under Oracle Lifetime Sustaining Support)