After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 745844 - OpenVPN activation crash
OpenVPN activation crash
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: VPN: openvpn
git master
Other Linux
: High critical
: ---
Assigned To: Lubomir Rintel
NetworkManager maintainer(s)
Depends on:
Blocks: nm-review
 
 
Reported: 2015-03-08 15:38 UTC by Oleksii Shevchuk
Modified: 2015-04-22 08:00 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
[PATCH] nm-ip[64]-config: set ifindex when replacing a duplicate route (1.38 KB, text/plain)
2015-04-20 16:04 UTC, Lubomir Rintel 		Details

Description Oleksii Shevchuk 2015-03-08 15:38:43 UTC 
NetworkManager: 6b5de0ab5f2caedabb0e516c2a26b86c0f0b1002
nm-openvpn: 7cc7b1f319827dff7a36cd8e23c4bd3c2feddb55
openvpn: 2.3.6

Backtrace from coredump:

+ Trace 234820

  • #0 __GI_raise
    at ../sysdeps/unix/sysv/linux/raise.c line 55
  • #1 __GI_abort
    at abort.c line 89
  • #2 g_assertion_message
  • #3 g_assertion_message_expr
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/glib/gtestutils.c line 2307
  • #4 nm_route_manager_ip4_route_sync
    at nm-route-manager.c line 179
  • #5 nm_ip4_config_commit
    at nm-ip4-config.c line 296
  • #6 nm_vpn_connection_apply_config
    at vpn-manager/nm-vpn-connection.c line 927
  • #7 nm_vpn_connection_config_maybe_complete
    at vpn-manager/nm-vpn-connection.c line 974
  • #8 nm_vpn_connection_ip6_config_get
    at vpn-manager/nm-vpn-connection.c line 1416
  • #9 signal_cb
    at vpn-manager/nm-vpn-connection.c line 1618
  • #10 ffi_call_unix64
    from /usr/lib64/libffi.so.6
  • #11 ffi_call
    from /usr/lib64/libffi.so.6
  • #12 g_cclosure_marshal_generic
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/gobject/gclosure.c line 1448
  • #13 g_closure_invoke
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/gobject/gclosure.c line 768
  • #14 signal_emit_unlocked_R
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/gobject/gsignal.c line 3553
  • #15 g_signal_emit_valist
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/gobject/gsignal.c line 3309
  • #16 g_signal_emit
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/gobject/gsignal.c line 3365
  • #17 on_signal_received
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/gio/gdbusproxy.c line 917
  • #18 emit_signal_instance_in_idle_cb
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/gio/gdbusconnection.c line 3753
  • #19 g_main_dispatch
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/glib/gmain.c line 3111
  • #20 g_main_context_dispatch
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/glib/gmain.c line 3710
  • #21 g_main_context_iterate
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/glib/gmain.c line 3781
  • #22 g_main_loop_run
    at /tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/glib/gmain.c line 3975
  • #23 main
    at main.c line 460 






Comment 1


Oleksii Shevchuk





          2015-03-08 15:43:03 UTC
        



NetworkManager:ERROR:nm-route-manager.c:179:nm_route_manager_ip4_route_sync: assertion failed: (known_route->ifindex)






Comment 2


Lubomir Rintel





          2015-03-12 06:53:38 UTC
        



I am not able to reproduce this.

I'm wondering if you could run NetworkManager with --debug --log-level=DEBUG and attach the complete log?

Thank you!






Comment 3


Lubomir Rintel





          2015-03-12 06:56:58 UTC
        



And, if possible, please share as much from your OpenVPN configuration as you can. "nmcli c show <vpn-connection>" would be perfect.






Comment 4


Oleksii Shevchuk





          2015-03-12 22:05:59 UTC
        



I had this on client side:
[ipv4]
method=auto
dns-search=
route1=192.168.30.0/24,172.16.0.1

And this on server side:
push "route 192.168.30.0 255.255.255.0"

After removing 
route1=192.168.30.0/24,172.16.0.1
I didn't catch any crashes. Maybe that was a problem






Comment 5


Lubomir Rintel





          2015-04-20 16:04:31 UTC
        



Created attachment 302009 [details]
[PATCH] nm-ip[64]-config: set ifindex when replacing a duplicate route






Comment 6


Dan Williams





          2015-04-21 18:40:37 UTC
        



LGTM






Comment 7


Lubomir Rintel





          2015-04-22 08:00:44 UTC
        



d231162 nm-ip[64]-config: set ifindex when replacing a duplicate route