Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
accessing core files in this form is really cumbersome, because I don't have the same binaries on my machine.
Could you open the dump with `gdb /usr/sbin/NetworkManager core.NetworkManager.0.a85df14566484415ba44659e39c8c6ff.129289.1593442258000000` and show the full backtrace (with `bt`)? (make sure to install debug symbols first, so that the backtrace is meaningful).
Comment 3Beniamino Galvani
2020-07-02 12:45:30 UTC
#0 dhcp4_start (self=0x560c5b2e0750) at src/devices/nm-device.c:8383
8383 _LOGW (LOGD_DHCP4, "failure to start DHCP: %s", error->message);
[Current thread is 1 (Thread 0x7ff44679d200 (LWP 129289))]
(gdb) backtrace
#0 0x0000560c59f9a734 in dhcp4_start (self=0x560c5b2e0750) at src/devices/nm-device.c:8383
#1 0x0000560c59f9ae75 in nm_device_dhcp4_renew (self=self@entry=0x560c5b2e0750, release=release@entry=0) at src/devices/nm-device.c:8413
#2 0x0000560c59fa1bd0 in nm_device_update_dynamic_ip_setup (self=self@entry=0x560c5b2e0750) at src/devices/nm-device.c:3485
#3 0x0000560c59e73b18 in do_sleep_wake (self=self@entry=0x560c5b1b9090, sleeping_changed=sleeping_changed@entry=0) at src/nm-manager.c:6032
#4 0x0000560c59e73d43 in _internal_enable (enable=1, self=0x560c5b1b9090) at src/nm-manager.c:6150
#5 0x0000560c59e73d43 in enable_net_done_cb (chain=<optimized out>, context=0x560c5b295630, user_data=0x560c5b1b9090) at src/nm-manager.c:6184
#6 0x0000560c59e6afc5 in pk_call_cb (auth_manager=<optimized out>, call_id=<optimized out>, user_data=0x560c5b238e90, error=0x0, is_challenge=0, is_authorized=1) at src/nm-auth-utils.c:309
#7 0x0000560c59e6afc5 in pk_call_cb (auth_manager=<optimized out>, call_id=<optimized out>, is_authorized=1, is_challenge=0, error=0x0, user_data=0x560c5b238e90) at src/nm-auth-utils.c:271
#8 0x0000560c59e68f68 in _call_id_invoke_callback (call_id=0x560c5b260200, is_authorized=<optimized out>, is_challenge=<optimized out>, error=<optimized out>) at src/nm-auth-manager.c:154
#9 0x0000560c59e69059 in _call_on_idle (user_data=0x560c5b260200) at src/nm-auth-manager.c:269
#10 0x00007ff44463efbb in g_idle_dispatch () at /lib64/libglib-2.0.so.0
#11 0x00007ff44464267d in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#12 0x00007ff444642a48 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#13 0x00007ff444642d72 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#14 0x0000560c59e3d5a9 in main (argc=<optimized out>, argv=<optimized out>) at src/main.c:456
NetworkManager[129289]: <trace> [1593442258.2135] dbus-object[12e751b93e8f0a84]: export: "/org/freedesktop/NetworkManager/DHCP4Config/14"
NetworkManager[129289]: ((src/platform/nmp-object.c:1920)): assertion '<dropped>' failed
NetworkManager[129289]: <warn> [1593442258.2140] device (br-ex): ipv4.dhcp-client-id: failure to generate client id (missing link-layer address). Use random client id
NetworkManager[129289]: <debug> [1593442258.2140] device[3d71857238195383] (br-ex): ipv4.dhcp-client-id: use "mac" client ID: 00:d9:11:4e:76:9e:02:c5:d0:b3:00:0e:6b:ab:cc:7a
NetworkManager[129289]: ((src/dhcp/nm-dhcp-manager.c:237)): assertion '<dropped>' failed
systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV
Comment 4Beniamino Galvani
2020-07-02 15:59:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4499