RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1592251 - [abrt] [faf] NetworkManager: raise(): /usr/sbin/NetworkManager killed by 5
Summary: [abrt] [faf] NetworkManager: raise(): /usr/sbin/NetworkManager killed by 5
Keywords:
Status: CLOSED DUPLICATE of bug 1543871
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: sushil kulkarni
QA Contact: Desktop QE
URL: http://faf.lab.eng.brq.redhat.com/faf...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-18 09:14 UTC by Vladimir Benes
Modified: 2018-06-18 09:24 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-18 09:24:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vladimir Benes 2018-06-18 09:14:17 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/03a906395b8bffa314dee9690e1242d7f390a661/

Comment 2 Beniamino Galvani 2018-06-18 09:24:42 UTC
1 	raise 	/lib64/libpthread.so.0 	0x10930
2 	g_logv 	/lib64/libglib-2.0.so.0 	0x56a00
3 	g_log 	/lib64/libglib-2.0.so.0 	0x56b60
4 	_nm_g_return_if_fail_warning.constprop.0 	/usr/sbin/NetworkManager 	0x35f3c
5 	nm_device_factory_manager_find_factory_for_connection 	/usr/sbin/NetworkManager 	0x141ae8
6 	nm_manager_get_connection_iface 	/usr/sbin/NetworkManager 	0x5c658
7 	check_connection_compatible 	/usr/sbin/NetworkManager 	0x11d870
8 	check_connection_compatible 	/usr/lib64/NetworkManager/libnm-device-plugin-ovs.so 	0x896c
9 	nm_device_check_connection_compatible 	/usr/sbin/NetworkManager 	0x123534
10 	nm_device_check_connection_available 	/usr/sbin/NetworkManager 	0x12efc0
11 	nm_device_recheck_available_connections 	/usr/sbin/NetworkManager 	0x12f368
12 	_set_state_full 	/usr/sbin/NetworkManager 	0x132994
13 	del_iface_cb 	/usr/lib64/NetworkManager/libnm-device-plugin-ovs.so 	0x8d78
14 	_transact_cb 	/usr/lib64/NetworkManager/libnm-device-plugin-ovs.so 	0x5c30
15 	ovsdb_disconnect 	/usr/lib64/NetworkManager/libnm-device-plugin-ovs.so 	0x4c5c
16 	dispose 	/usr/lib64/NetworkManager/libnm-device-plugin-ovs.so 	0x6338
17 	g_object_unref 	/lib64/libgobject-2.0.so.0 	0x15d5c
18 	_nm_singleton_instance_destroy 	/usr/sbin/NetworkManager 	0x389b4
19 	_dl_fini 	/lib/ld-linux-aarch64.so.1 	0xe958
20 	__run_exit_handlers 	/lib64/libc.so.6 	0x3879c
21 	on_exit 	/lib64/libc.so.6 	0x387c4
22 	main 	/usr/sbin/NetworkManager 	0x38fe0

*** This bug has been marked as a duplicate of bug 1543871 ***


Note You need to log in before you can comment on or make changes to this bug.