connman.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
To: Daniel Wagner <wagi@monom.org>
Cc: Klaus Ethgen <klaus@ethgen.ch>, connman@lists.linux.dev
Subject: Re: Too many wlans
Date: Sun, 19 Dec 2021 18:23:55 +0100	[thread overview]
Message-ID: <CAOf5uwnvYzk0ZX3Ca_FSQLM4sf4mp_UtBStoUcdoeH9L8DJvOQ@mail.gmail.com> (raw)
In-Reply-To: <20211219172226.73tupsi7z24hkiiy@beryllium.lan>

Hi

On Sun, Dec 19, 2021 at 6:22 PM Daniel Wagner <wagi@monom.org> wrote:
>
> Hi,
>
> On Mon, Dec 06, 2021 at 02:10:18PM +0100, Klaus Ethgen wrote:
> > Hello,
> >
> > I found a bug in connman when too many networks are stored into
> > /var/lib/connman.
> >
> > I shuttle between different locations and today, connman stopped showing
> > networks at all. After some debugging, I found the following Messages in
> > wpa_supplicant debug output:
> > ```
> > wlan0: Event SCAN_RESULTS (3) received
> > Scan results did not fit - trying larger buffer (8192 bytes)
> > Scan results did not fit - trying larger buffer (16384 bytes)
> > Scan results did not fit - trying larger buffer (32768 bytes)
> > Scan results did not fit - trying larger buffer (65535 bytes)
> > ioctl[SIOCGIWSCAN]: Argument list too long
> > wlan0: Failed to get scan results
> > wlan0: Failed to get scan results - try scanning again
> > ```
> >
> > The `Argument list too long` got my interest and I looked into
> > /var/lib/connman finding 104 directories in the form
> > wifi_XXXXXXXXXXXX_XXXXXXXX_managed_XXXXXXXXX.
>
> Do you have the exact log for this? ConnMan uses GLib APIs for iterating
> over files and directory. I would be very surprised if GLib is not able
> to deal with this small numbers of entries.
>
> > After deleting all directories and restarting connman, everything went
> > back to working state.
>
> I don't think 104 known networks are a real resource problem as long
> there is enough memory in the system. But even then, I don't think
> ConnMan needs more than a few kb per known network.
>
> > So, if that directories is an issue, could it be cleaned up?
>
> Yes you can cleanup the directories but it's recommended not to do this
> while ConnMan is running.
>
> I think by deleting all known networks and previously corrupted? entry
> got removed which prevented the proper working before.
>

I have respin the patches on network removal. I will send

Michael

> Daniel
>


-- 
Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
michael@amarulasolutions.com
__________________________________

Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
info@amarulasolutions.com
www.amarulasolutions.com

  reply	other threads:[~2021-12-19 17:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 13:10 Too many wlans Klaus Ethgen
2021-12-19 17:22 ` Daniel Wagner
2021-12-19 17:23   ` Michael Nazzareno Trimarchi [this message]
2021-12-19 17:31     ` Daniel Wagner
2021-12-19 17:41       ` Michael Nazzareno Trimarchi
2021-12-19 17:42         ` Daniel Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOf5uwnvYzk0ZX3Ca_FSQLM4sf4mp_UtBStoUcdoeH9L8DJvOQ@mail.gmail.com \
    --to=michael@amarulasolutions.com \
    --cc=connman@lists.linux.dev \
    --cc=klaus@ethgen.ch \
    --cc=wagi@monom.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).