Description of problem: Trying out the latest GlusterFlow translator with Glupy and GlusterFS (compiled from git). Now getting SIGSEGV. Not a good sign. :( Version-Release number of selected component: glusterfs-3git-1.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/sbin/glusterfs -s localhost --volfile-id gluster/nfs -p /var/lib/glusterd/nfs/run/nfs.pid -l /var/log/glusterfs/nfs.log -S /var/run/6887ecd34e9ac064dfca26d730f5bea9.socket crash_function: CThunkObject_dealloc executable: /usr/sbin/glusterfsd kernel: 3.11.6-200.0.bz953211.1.fc19.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 CThunkObject_dealloc at /usr/src/debug/Python-2.7.5/Modules/_ctypes/callbacks.c:24 #1 _ctypes_alloc_callback at /usr/src/debug/Python-2.7.5/Modules/_ctypes/callbacks.c:493 #2 PyCFuncPtr_new at /usr/src/debug/Python-2.7.5/Modules/_ctypes/_ctypes.c:3498 #3 type_call at /usr/src/debug/Python-2.7.5/Objects/typeobject.c:729 #4 PyObject_Call at /usr/src/debug/Python-2.7.5/Objects/abstract.c:2529 #5 do_call at /usr/src/debug/Python-2.7.5/Python/ceval.c:4316 #6 call_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4121 #7 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:2740 #8 PyEval_EvalCodeEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:3330 #9 function_call at /usr/src/debug/Python-2.7.5/Objects/funcobject.c:526
Created attachment 819954 [details] File: backtrace
Created attachment 819955 [details] File: cgroup
Created attachment 819956 [details] File: core_backtrace
Created attachment 819957 [details] File: dso_list
Created attachment 819958 [details] File: environ
Created attachment 819959 [details] File: limits
Created attachment 819960 [details] File: maps
Created attachment 819961 [details] File: open_fds
Created attachment 819962 [details] File: proc_pid_status
Created attachment 819963 [details] File: var_log_messages
At a guess, this could be related to bug 1010241.
Seems related to your Glupy work? Is this still current, have you found the cause, can it be closed?
Hmmm, the Glupy code and related parts have changed quite a lot since this. Probably best to close this, and I'll open another bug later on if it's needed, when I get up to working on GlusterFlow again.