Your message dated Mon, 30 Mar 2015 23:50:18 +0200
with message-id <[email protected]>
and subject line Re: network-manager: should automatically restart after asserts
has caused the Debian Bug report #384914,
regarding network-manager: should automatically restart after asserts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
384914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384914
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.6.4-1
Severity: important

Hi,

There is generally nothing wrong with quitting on asserts. Those should not 
really be used in production code as there is almost always a better way out 
than to  simply exit. An example follows:
Aug 27 22:52:06 yavin NetworkManager: file NetworkManagerPolicy.c: line 62 
(nm_policy_activation_finish): assertion failed: (dev)

This was caused by accessing a network with WPA2/EAP-TTLS (not really present, 
wanted to preset the setting) and just before finishing switching to another 
network.

I guess that NetworkManager could/should be automatically restarted in such 
cases or remove such asserts and find a better way of rolling back.

HS

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.8-yavin
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages network-manager depends on:
ii  dbus                    0.62-4           simple interprocess messaging 
syst
ii  dhcdbd                  1.14-2           dbus interface to the ISC DHCP 
cli
ii  hal                     0.5.7.1-1        Hardware Abstraction Layer
ii  ifupdown                0.6.7            high level tools to configure 
netw
ii  iproute                 20051007-4       Professional tools to control the 
ii  iputils-arping          3:20020927-3     Tool to send ICMP echo requests 
to
ii  libc6                   2.3.6-15         GNU C Library: Shared libraries
ii  libdbus-1-2             0.62-4           simple interprocess messaging 
syst
ii  libdbus-glib-1-2        0.62-4           simple interprocess messaging 
syst
ii  libgcrypt11             1.2.2-3          LGPL Crypto library - runtime 
libr
ii  libglib2.0-0            2.10.3-3         The GLib library of C routines
ii  libgpg-error0           1.2-1            library for common error values 
an
ii  libhal1                 0.5.7-2          Hardware Abstraction Layer - 
share
ii  libiw28                 28-1             Wireless tools - library
ii  libnl1-pre6             1.0~pre6~svn30-1 Library for dealing with netlink 
s
ii  libnm-util0             0.6.3-2          network management framework 
(shar
ii  lsb-base                3.1-14           Linux Standard Base 3.1 init 
scrip
ii  wpasupplicant           0.5.4-5          Client support for WPA and WPA2 
(I

network-manager recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 0.9.10.0-5

On Sun, 27 Aug 2006 23:03:23 +0200 Hendrik Sattler
<[email protected]> wrote:
> Package: network-manager
> Version: 0.6.4-1
> Severity: important
> 
> Hi,
> 
> There is generally nothing wrong with quitting on asserts. Those should not 
> really be used in production code as there is almost always a better way out 
> than to  simply exit. An example follows:
> Aug 27 22:52:06 yavin NetworkManager: file NetworkManagerPolicy.c: line 62 
> (nm_policy_activation_finish): assertion failed: (dev)
> 
> This was caused by accessing a network with WPA2/EAP-TTLS (not really 
> present, 
> wanted to preset the setting) and just before finishing switching to another 
> network.
> 
> I guess that NetworkManager could/should be automatically restarted in such 
> cases or remove such asserts and find a better way of rolling back.

sysvinit doesn't provide such a functionality, but systemd does if the
daemon opts into that.

The NetworkManager.service unit file has

Restart=on-failure

so will be restarted in cases like you described.
Therefor closing.
This was added in 0.9.10.0-5

network-manager (0.9.10.0-5) unstable; urgency=medium

  * Cherry-pick upstream commit which prevents breaking PtP TUN
interfaces by
    not overriding external route metrics. (Closes: #767002)
  * Cherry-pick upstream commit which tells systemd to restart
NetworkManager
    if it exits with a failure. (Closes: #773213)

 -- Michael Biebl <[email protected]>  Wed, 31 Dec 2014 01:10:08 +0100



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

Reply via email to