Bug 986737

Summary: [abrt] ypbind-1.37.1-3.fc19: test_bindings_once: Process /usr/sbin/ypbind was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Eugene Kanter <ekanter>
Component: ypbindAssignee: Matej Mužila <mmuzila>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: ekanter, hhorak
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e934fcf0076d7cf8c8c2e642b9c4b912e6652d67
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 16:17:41 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: var_log_messages none

Description Eugene Kanter 2013-07-22 01:22:36 UTC
Description of problem:
I don't know what exactly caused this problem. It is possible that network cable was disconnected mentarily.

Version-Release number of selected component:
ypbind-1.37.1-3.fc19

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/sbin/ypbind -n
crash_function: test_bindings_once
executable:     /usr/sbin/ypbind
kernel:         3.9.9-302.fc19.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 test_bindings_once at serv_list.c:1271
 #1 ypbindproc_domain at ypbind_server.c:88
 #2 ypbindprog_2 at ypbind_svc.c:176
 #3 svc_getreq_common at svc.c:534
 #4 svc_getreq_poll at svc.c:460
 #5 svc_run at svc_run.c:96

Comment 1 Eugene Kanter 2013-07-22 01:22:39 UTC
Created attachment 776635 [details]
File: backtrace

Comment 2 Eugene Kanter 2013-07-22 01:22:41 UTC
Created attachment 776636 [details]
File: cgroup

Comment 3 Eugene Kanter 2013-07-22 01:22:43 UTC
Created attachment 776637 [details]
File: core_backtrace

Comment 4 Eugene Kanter 2013-07-22 01:22:46 UTC
Created attachment 776638 [details]
File: dso_list

Comment 5 Eugene Kanter 2013-07-22 01:22:48 UTC
Created attachment 776639 [details]
File: environ

Comment 6 Eugene Kanter 2013-07-22 01:22:51 UTC
Created attachment 776640 [details]
File: limits

Comment 7 Eugene Kanter 2013-07-22 01:22:53 UTC
Created attachment 776641 [details]
File: maps

Comment 8 Eugene Kanter 2013-07-22 01:22:56 UTC
Created attachment 776642 [details]
File: open_fds

Comment 9 Eugene Kanter 2013-07-22 01:22:59 UTC
Created attachment 776643 [details]
File: proc_pid_status

Comment 10 Eugene Kanter 2013-07-22 01:23:02 UTC
Created attachment 776644 [details]
File: var_log_messages

Comment 11 Honza Horak 2013-07-25 15:47:40 UTC
Thanks for reporting, but I'm not able to reproduce it unfortunately. Have you encountered this failure only once or you can reproduce it?

Comment 12 Eugene Kanter 2013-07-26 19:59:22 UTC
It was a power failure on the switch between this machine and NIS server. The machine also has two network cards if it makes a difference and I believe both were plugged in at the time, both under default NetworkManager control.

Comment 13 Fedora Admin XMLRPC Client 2014-09-11 15:17:53 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 14 Fedora End Of Life 2015-01-09 19:02:20 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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 15 Fedora End Of Life 2015-02-17 16:17:41 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.