Your message dated Mon, 3 Oct 2016 14:10:03 +0100
with message-id <[email protected]>
and subject line Re: network-manager: Fails to connect to wifi, "Too many open
files"
has caused the Debian Bug report #836774,
regarding network-manager: Fails to connect to wifi, "Too many open files"
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.)
--
836774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836774
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.4.0-3
Severity: important
After a dist-upgrade network-manager will no longer connect to my wifi.
The logs say "Too many open files in system", but this doesn't seem
likely, because nothing else is broken (except for a minor GTK3 issue
which seems irrelevant). The connection works if I add it to
/etc/network/interfaces and use ifup. I'm attaching a log from
journalctl, because that seems much more useful than /var/log/daemon.log
as suggested on
<https://wiki.gnome.org/Projects/NetworkManager/Debugging>. Their advice
about getting more info from wpa_supplicant doesn't apply to current
Debian either (adding -f... to the dbus file doesn't do anything), I
hope you've got enough in this log.
I found #832093, which looks like a similar issue at first, but I think
this is something different. But that mentions "opting out of
nm-wait-online" to avoid network issues holding up the boot sequence.
Please could you explain how I do that because, while I'm not a systemd
hater, I still don't know much about using it.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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.115
ii dbus 1.10.10-1
ii init-system-helpers 1.42
ii libaudit1 1:2.6.6-1
ii libbluetooth3 5.36-1+b2
ii libc6 2.24-2
ii libglib2.0-0 2.49.6-1
ii libgnutls30 3.5.3-4
ii libgudev-1.0-0 230-3
ii libmm-glib0 1.6.0-1
ii libndp0 1.6-1
ii libnewt0.52 0.52.18-3
ii libnl-3-200 3.2.27-1
ii libnm0 1.4.0-3
ii libpam-systemd 231-5
ii libpolkit-agent-1-0 0.105-16
ii libpolkit-gobject-1-0 0.105-16
ii libreadline6 6.3-8+b4
ii libselinux1 2.5-3
ii libsoup2.4-1 2.55.90-1
ii libsystemd0 231-5
ii libteamdctl0 1.26-1
ii libuuid1 2.28.1-1
ii lsb-base 9.20160629
ii policykit-1 0.105-16
ii udev 231-5
ii wpasupplicant 2.5-2+v2.4-2
Versions of packages network-manager recommends:
ii crda 3.13-1+b1
ii dnsmasq-base 2.76-4
ii iptables 1.6.0-3
ii iputils-arping 3:20150815-2
ii isc-dhcp-client 4.3.4-1
pn modemmanager <none>
ii ppp 2.4.7-1+3
Versions of packages network-manager suggests:
pn libteam-utils <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
It seems to be working again as of version 1.4.2-1. It's difficult to
tell what change might have fixed it because changelog.gz is obsolete (I
feel this might be considered another bug?) and upstream's git log is tl;dr.
--
TH
--- End Message ---
