Bug 892035

Summary: [abrt] mongodb-2.2.2-1.fc18: _IO_new_fclose: Process /usr/bin/mongodump was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Michael S. <misc>
Component: mongodbAssignee: Nathaniel McCallum <nathaniel>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: admiller, databases-maint, jim, nathaniel, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2d08b979bb471ae88347dfe2ab31049b12f75e0d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 14:24:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: smolt_data
none
File: var_log_messages none

Description Michael S. 2013-01-04 22:13:26 UTC 
Description of problem:
I was trying to trigger a issue in a script using mongodb dump utilitie, so I created a directory ~/tmp/t/ , then cd to it, ran mongodump a first time, then :
chattr +i  dump/stickshift_broker_dev/*

# mongodump 
connected to: 127.0.0.1
Fri Jan  4 23:06:33 all dbs
Fri Jan  4 23:06:33 DATABASE: stickshift_broker_dev	 to 	dump/stickshift_broker_dev
Fri Jan  4 23:06:33 	stickshift_broker_dev.system.users to dump/stickshift_broker_dev/system.users.bson
Erreur de segmentation (core dumped)

So mongodb crash if we try to write in a directory where it cannot write ( due to chattr +i )

Version-Release number of selected component:
mongodb-2.2.2-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        mongodump
crash_function: _IO_new_fclose
executable:     /usr/bin/mongodump
kernel:         3.6.11-3.fc18.x86_64
remote_result:  NOTFOUND
uid:            0

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 _IO_new_fclose at iofclose.c:54
 #1 Dump::writeCollectionFile at src/mongo/tools/dump.cpp:132
 #2 Dump::go at src/mongo/tools/dump.cpp:233
 #3 Dump::run at src/mongo/tools/dump.cpp:514
 #4 mongo::Tool::main at src/mongo/tools/tool.cpp:266
Comment 1 Michael S. 2013-01-04 22:13:29 UTC 
Created attachment 672591 [details]
File: backtrace
Comment 2 Michael S. 2013-01-04 22:13:31 UTC 
Created attachment 672592 [details]
File: cgroup
Comment 3 Michael S. 2013-01-04 22:13:33 UTC 
Created attachment 672593 [details]
File: core_backtrace
Comment 4 Michael S. 2013-01-04 22:13:35 UTC 
Created attachment 672594 [details]
File: dso_list
Comment 5 Michael S. 2013-01-04 22:13:37 UTC 
Created attachment 672595 [details]
File: environ
Comment 6 Michael S. 2013-01-04 22:13:40 UTC 
Created attachment 672596 [details]
File: limits
Comment 7 Michael S. 2013-01-04 22:13:42 UTC 
Created attachment 672597 [details]
File: maps
Comment 8 Michael S. 2013-01-04 22:13:44 UTC 
Created attachment 672598 [details]
File: open_fds
Comment 9 Michael S. 2013-01-04 22:13:46 UTC 
Created attachment 672599 [details]
File: proc_pid_status
Comment 10 Michael S. 2013-01-04 22:13:48 UTC 
Created attachment 672600 [details]
File: smolt_data
Comment 11 Michael S. 2013-01-04 22:13:50 UTC 
Created attachment 672601 [details]
File: var_log_messages
Comment 12 Troy Dawson 2013-03-01 21:19:15 UTC 
Did this get fixed with the 2.2.3 update?
Comment 13 Fedora End Of Life 2013-12-21 10:11:18 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Fedora End Of Life 2014-02-05 14:24:31 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.