Your message dated Sun, 28 Oct 2018 20:26:27 +0100
with message-id <[email protected]>
and subject line Re: network-manager: fails to start: "Failed at step NAMESPACE"
has caused the Debian Bug report #820174,
regarding network-manager: fails to start: "Failed at step NAMESPACE"
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.)
--
820174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820174
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.1.92-1
Severity: important
Dear Maintainer,
The upgrade from 1.1.91-3 to 1.1.92-1 failed, with
NetworkManager.service unable to start the service. The logs say
Apr 06 10:07:14 heffalump.sk2.org systemd[1]: Starting Network Manager...
-- Subject: Unit NetworkManager.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager.service has begun starting up.
Apr 06 10:07:14 heffalump.sk2.org systemd[22314]: NetworkManager.service:
Failed at step NAMESPACE spawning /usr/sbin/NetworkManager: Invalid argument
-- Subject: Process /usr/sbin/NetworkManager could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/sbin/NetworkManager could not be executed and failed.
--
-- The error number returned by this process is 22.
Apr 06 10:07:14 heffalump.sk2.org systemd[1]: NetworkManager.service: Main
process exited, code=exited, status=226/NAMESPACE
Apr 06 10:07:14 heffalump.sk2.org systemd[1]: Failed to start Network Manager.
-- Subject: Unit NetworkManager.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager.service has failed.
--
-- The result is failed.
Apr 06 10:07:14 heffalump.sk2.org systemd[1]: NetworkManager.service: Unit
entered failed state.
Apr 06 10:07:14 heffalump.sk2.org systemd[1]: NetworkManager.service: Failed
with result 'exit-code'.
How should I go about debugging this?
Regards,
Stephen
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing'), (500, 'stable'), (200,
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.4.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages network-manager depends on:
ii adduser 3.114
ii dbus 1.10.8-1
ii init-system-helpers 1.29
ii isc-dhcp-client 4.3.3-8
ii libbluetooth3 5.36-1
ii libc6 2.22-5
ii libglib2.0-0 2.48.0-1
ii libgnutls30 3.4.10-4
ii libgudev-1.0-0 230-3
ii libmm-glib0 1.4.14-1
ii libndp0 1.4-2
ii libnewt0.52 0.52.18-3
ii libnl-3-200 3.2.27-1
ii libnm0 1.1.92-1
ii libpam-systemd 229-3
ii libpolkit-agent-1-0 0.105-14.1
ii libpolkit-gobject-1-0 0.105-14.1
ii libreadline6 6.3-8+b4
ii libsoup2.4-1 2.52.2-1
ii libsystemd0 229-3
ii libteamdctl0 1.23-1
ii libuuid1 2.27.1-6
ii lsb-base 9.20160110
ii policykit-1 0.105-14.1
ii udev 229-3
ii wpasupplicant 2.3-2.3
Versions of packages network-manager recommends:
ii crda 3.13-1+b1
ii dnsmasq-base 2.75-1
ii iptables 1.6.0-2
ii iputils-arping 3:20150815-2
pn modemmanager <none>
ii ppp 2.4.7-1+2
Versions of packages network-manager suggests:
pn libteam-utils <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Michael,
On Thu, 25 Oct 2018 08:07:46 +0200, Michael Biebl <[email protected]> wrote:
> On Wed, 06 Apr 2016 10:13:07 +0200 Stephen Kitt <[email protected]> wrote:
> > Package: network-manager
> > Version: 1.1.92-1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > The upgrade from 1.1.91-3 to 1.1.92-1 failed, with
> > NetworkManager.service unable to start the service. The logs say
> >
> > Apr 06 10:07:14 heffalump.sk2.org systemd[1]: Starting Network Manager...
> > -- Subject: Unit NetworkManager.service has begun start-up
> > -- Defined-By: systemd
> > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> > --
> > -- Unit NetworkManager.service has begun starting up.
> > Apr 06 10:07:14 heffalump.sk2.org systemd[22314]: NetworkManager.service:
> > Failed at step NAMESPACE spawning /usr/sbin/NetworkManager: Invalid
> > argument -- Subject: Process /usr/sbin/NetworkManager could not be
> > executed -- Defined-By: systemd -- Support:
> > http://lists.freedesktop.org/mailman/listinfo/systemd-devel --
> > -- The process /usr/sbin/NetworkManager could not be executed and failed.
> > --
> > -- The error number returned by this process is 22.
> > Apr 06 10:07:14 heffalump.sk2.org systemd[1]: NetworkManager.service:
> > Main process exited, code=exited, status=226/NAMESPACE Apr 06 10:07:14
> > heffalump.sk2.org systemd[1]: Failed to start Network Manager. --
> > Subject: Unit NetworkManager.service has failed -- Defined-By: systemd
> > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> > --
> > -- Unit NetworkManager.service has failed.
> > --
> > -- The result is failed.
> > Apr 06 10:07:14 heffalump.sk2.org systemd[1]: NetworkManager.service:
> > Unit entered failed state. Apr 06 10:07:14 heffalump.sk2.org systemd[1]:
> > NetworkManager.service: Failed with result 'exit-code'.
> >
> >
> > How should I go about debugging this?
>
> I wonder if you can still reproduce the issue?
I’d never revisited it, so I still had my overrides in place... I stopped
NetworkManager.service, removed my overrides, started it again (verifying
that it used /lib/systemd/system/NetworkManager.service directly), and
everything seems to be working, so it looks like this issue is fixed. I’m
closing it with this email.
Thanks for the ping,
Stephen
pgpAdmGoTaxJM.pgp
Description: OpenPGP digital signature
--- End Message ---
