[Gluster-devel] Core from gNFS process

[Raghavendra Talur]

On Sat, Jan 16, 2016 at 2:25 AM, Vijay Bellur <vbellur at redhat.com> wrote:

> On 01/15/2016 08:38 AM, Soumya Koduri wrote:
>
>>
>>
>>
>> On 01/15/2016 06:52 PM, Soumya Koduri wrote:
>>
>>>
>>>
>>> On 01/14/2016 08:41 PM, Vijay Bellur wrote:
>>>
>>>> On 01/14/2016 04:11 AM, Jiffin Tony Thottan wrote:
>>>>
>>>>>
>>>>>
>>>>> On 14/01/16 14:28, Jiffin Tony Thottan wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The core generated when encryption xlator is enabled
>>>>>>
>>>>>> [2016-01-14 08:13:15.740835] E
>>>>>> [crypt.c:4298:master_set_master_vol_key] 0-test1-crypt: FATAL: missing
>>>>>> master key
>>>>>> [2016-01-14 08:13:15.740859] E [MSGID: 101019]
>>>>>> [xlator.c:429:xlator_init] 0-test1-crypt: Initialization of volume
>>>>>> 'test1-crypt' failed, review your volfile again
>>>>>> [2016-01-14 08:13:15.740890] E [MSGID: 101066]
>>>>>> [graph.c:324:glusterfs_graph_init] 0-test1-crypt: initializing
>>>>>> translator failed
>>>>>> [2016-01-14 08:13:15.740904] E [MSGID: 101176]
>>>>>> [graph.c:670:glusterfs_graph_activate] 0-graph: init failed
>>>>>> [2016-01-14 08:13:15.741676] W [glusterfsd.c:1231:cleanup_and_exit]
>>>>>> (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x307) [0x40d287]
>>>>>> -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x117) [0x4086c7]
>>>>>> -->/usr/sbin/glusterfs(cleanup_and_exit+0x4d) [0x407e1d] ) 0-:
>>>>>> received signum (0), shutting down
>>>>>>
>>>>>>
>>>>>>
>>>>> Forgot to mention this last mail,  for crypt xlator needs master key
>>>>> before enabling the translator which cause the issue
>>>>> --
>>>>>
>>>>
>>>> Irrespective of the problem, the nfs process should not crash. Can we
>>>> check why there is a memory corruption during cleanup_and_exit()?
>>>>
>>>> That's right. This issue was reported quite a few times earlier in
>>> gluster-devel and it is not specific to gluster-nfs process. As updated
>>> in [1], we have raised bug1293594[2] against lib-gcc team to further
>>> investigate this.
>>>
>>
> The segmentation fault in gcc is while attempting to print a backtrace
> upon glusterfs receiving a SIGSEGV. It would be good to isolate the reason
> for the initial SIGSEGV whose signal handler causes the further crash.


I wasn't able to check this today. Will check tomorrow.


>
>
> -Vijay
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20160118/9d7a7b71/attachment.html>