[Bugs] [Bug 1282465] New: [Backup]: Crash observed when keyboard interrupt is encountered in the middle of any glusterfind command
bugzilla at redhat.com
bugzilla at redhat.com
Mon Nov 16 14:01:01 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1282465
Bug ID: 1282465
Summary: [Backup]: Crash observed when keyboard interrupt is
encountered in the middle of any glusterfind command
Product: GlusterFS
Version: 3.7.5
Component: glusterfind
Severity: medium
Assignee: bugs at gluster.org
Reporter: avishwan at redhat.com
QA Contact: bugs at gluster.org
CC: avishwan at redhat.com, bugs at gluster.org,
khiremat at redhat.com, rhs-bugs at redhat.com,
sanandpa at redhat.com
Depends On: 1228079, 1243812
Blocks: 1223636
+++ This bug was initially created as a clone of Bug #1243812 +++
+++ This bug was initially created as a clone of Bug #1228079 +++
Description of problem:
While executing any of the glusterfind CLI commands, if Ctrl+C is pressed
before the command is completed, it results in a crash with the below trace:
[root at dhcp43-48 ~]# glusterfind pre sessn1 nash outn1.txt --output-prefix /tmp/
-N
^CProcess Process-3:
Traceback (most recent call last):
File "/usr/lib64/python2.6/multiprocessing/process.py", line 232, in
_bootstrap
Process Process-2:
Traceback (most recent call last):
File "/usr/lib64/python2.6/multiprocessing/process.py", line 232, in
_bootstrap
Traceback (most recent call last):
File "/usr/bin/glusterfind", line 17, in <module>
main()
File "/usr/libexec/glusterfs/glusterfind/main.py", line 519, in main
globals()["mode_" + args.mode](session_dir, args)
File "/usr/libexec/glusterfs/glusterfind/main.py", line 380, in mode_pre
run_cmd_nodes("pre", args, start=start)
File "/usr/libexec/glusterfs/glusterfind/main.py", line 161, in run_cmd_nodes
p.join()
File "/usr/lib64/python2.6/multiprocessing/process.py", line 119, in join
Process Process-1:
Traceback (most recent call last):
File "/usr/lib64/python2.6/multiprocessing/process.py", line 232, in
_bootstrap
Process Process-4:
Traceback (most recent call last):
File "/usr/lib64/python2.6/multiprocessing/process.py", line 232, in
_bootstrap
self.run()
File "/usr/lib64/python2.6/multiprocessing/process.py", line 88, in run
self._target(*self._args, **self._kwargs)
File "/usr/libexec/glusterfs/glusterfind/main.py", line 65, in node_cmd
execute(cmd, exit_msg="%s - %s failed" % (host, task), logger=logger)
File "/usr/libexec/glusterfs/glusterfind/utils.py", line 164, in execute
(out, err) = p.communicate()
File "/usr/lib64/python2.6/subprocess.py", line 732, in communicate
self.run()
File "/usr/lib64/python2.6/multiprocessing/process.py", line 88, in run
self._target(*self._args, **self._kwargs)
File "/usr/libexec/glusterfs/glusterfind/main.py", line 65, in node_cmd
execute(cmd, exit_msg="%s - %s failed" % (host, task), logger=logger)
File "/usr/libexec/glusterfs/glusterfind/utils.py", line 164, in execute
(out, err) = p.communicate()
File "/usr/lib64/python2.6/subprocess.py", line 732, in communicate
res = self._popen.wait(timeout)
File "/usr/lib64/python2.6/multiprocessing/forking.py", line 122, in wait
self.run()
File "/usr/lib64/python2.6/multiprocessing/process.py", line 88, in run
self._target(*self._args, **self._kwargs)
File "/usr/libexec/glusterfs/glusterfind/main.py", line 65, in node_cmd
execute(cmd, exit_msg="%s - %s failed" % (host, task), logger=logger)
File "/usr/libexec/glusterfs/glusterfind/utils.py", line 164, in execute
(out, err) = p.communicate()
File "/usr/lib64/python2.6/subprocess.py", line 732, in communicate
self.run()
File "/usr/lib64/python2.6/multiprocessing/process.py", line 88, in run
self._target(*self._args, **self._kwargs)
File "/usr/libexec/glusterfs/glusterfind/main.py", line 65, in node_cmd
execute(cmd, exit_msg="%s - %s failed" % (host, task), logger=logger)
File "/usr/libexec/glusterfs/glusterfind/utils.py", line 164, in execute
(out, err) = p.communicate()
File "/usr/lib64/python2.6/subprocess.py", line 732, in communicate
stdout, stderr = self._communicate(input, endtime)
File "/usr/lib64/python2.6/subprocess.py", line 1316, in _communicate
stdout, stderr = self._communicate_with_poll(input, endtime)
File "/usr/lib64/python2.6/subprocess.py", line 1388, in
_communicate_with_poll
ready = poller.poll(self._remaining_time(endtime))
KeyboardInterrupt
stdout, stderr = self._communicate(input, endtime)
File "/usr/lib64/python2.6/subprocess.py", line 1316, in _communicate
stdout, stderr = self._communicate_with_poll(input, endtime)
File "/usr/lib64/python2.6/subprocess.py", line 1388, in
_communicate_with_poll
ready = poller.poll(self._remaining_time(endtime))
KeyboardInterrupt
stdout, stderr = self._communicate(input, endtime)
File "/usr/lib64/python2.6/subprocess.py", line 1316, in _communicate
stdout, stderr = self._communicate_with_poll(input, endtime)
File "/usr/lib64/python2.6/subprocess.py", line 1388, in
_communicate_with_poll
ready = poller.poll(self._remaining_time(endtime))
KeyboardInterrupt
stdout, stderr = self._communicate(input, endtime)
File "/usr/lib64/python2.6/subprocess.py", line 1316, in _communicate
stdout, stderr = self._communicate_with_poll(input, endtime)
File "/usr/lib64/python2.6/subprocess.py", line 1388, in
_communicate_with_poll
ready = poller.poll(self._remaining_time(endtime))
KeyboardInterrupt
return self.poll(0)
File "/usr/lib64/python2.6/multiprocessing/forking.py", line 107, in poll
pid, sts = os.waitpid(self.pid, flag)
KeyboardInterrupt
Version-Release number of selected component (if applicable):
glusterfs-3.7.0-3.el6rhs.x86_64
How reproducible: Always
--- Additional comment from Aravinda VK on 2015-07-16 08:29:56 EDT ---
Upstream Patch is sent
http://review.gluster.org/#/c/11698/
--- Additional comment from Anand Avati on 2015-07-23 01:04:06 EDT ---
REVIEW: http://review.gluster.org/11698 (tools/glusterfind: Handle Keyboard
interrupt) posted (#2) for review on master by Aravinda VK
(avishwan at redhat.com)
--- Additional comment from Anand Avati on 2015-08-05 04:06:43 EDT ---
REVIEW: http://review.gluster.org/11698 (tools/glusterfind: Handle Keyboard
interrupt) posted (#3) for review on master by Aravinda VK
(avishwan at redhat.com)
--- Additional comment from Anand Avati on 2015-08-12 05:46:25 EDT ---
REVIEW: http://review.gluster.org/11698 (tools/glusterfind: Handle Keyboard
interrupt) posted (#4) for review on master by Aravinda VK
(avishwan at redhat.com)
--- Additional comment from Anand Avati on 2015-08-19 01:59:08 EDT ---
REVIEW: http://review.gluster.org/11698 (tools/glusterfind: Handle Keyboard
interrupt) posted (#5) for review on master by Aravinda VK
(avishwan at redhat.com)
--- Additional comment from Anand Avati on 2015-08-26 01:57:03 EDT ---
REVIEW: http://review.gluster.org/11698 (tools/glusterfind: Handle Keyboard
interrupt) posted (#6) for review on master by Aravinda VK
(avishwan at redhat.com)
--- Additional comment from Vijay Bellur on 2015-10-14 02:22:09 EDT ---
REVIEW: http://review.gluster.org/11698 (tools/glusterfind: Handle Keyboard
interrupt) posted (#9) for review on master by Aravinda VK
(avishwan at redhat.com)
--- Additional comment from Vijay Bellur on 2015-11-02 01:24:47 EST ---
REVIEW: http://review.gluster.org/11698 (tools/glusterfind: Handle Keyboard
interrupt) posted (#10) for review on master by Aravinda VK
(avishwan at redhat.com)
--- Additional comment from Vijay Bellur on 2015-11-16 00:35:08 EST ---
REVIEW: http://review.gluster.org/11698 (tools/glusterfind: Handle Keyboard
interrupt) posted (#13) for review on master by Aravinda VK
(avishwan at redhat.com)
--- Additional comment from Vijay Bellur on 2015-11-16 06:05:11 EST ---
REVIEW: http://review.gluster.org/11698 (tools/glusterfind: Handle Keyboard
interrupt) posted (#14) for review on master by Aravinda VK
(avishwan at redhat.com)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1223636
[Bug 1223636] 3.1 QE Tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1228079
[Bug 1228079] [Backup]: Crash observed when keyboard interrupt is
encountered in the middle of any glusterfind command
https://bugzilla.redhat.com/show_bug.cgi?id=1243812
[Bug 1243812] [Backup]: Crash observed when keyboard interrupt is
encountered in the middle of any glusterfind command
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list