All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Johnson <mjohnson459 at gmail.com>
To: iwd at lists.01.org
Subject: Re: DHCP renewal stops after disconnect
Date: Mon, 16 May 2022 10:38:34 +0100	[thread overview]
Message-ID: <CACsRnHVzAPXVDh2qSgGbpqo_yBAco+UHuehAZCouXbuVN7=zKQ@mail.gmail.com> (raw)
In-Reply-To: CACsRnHV6tmVL0051RjrST91qy+YghS0ZSUzhBbr-tdxkr-cpMA@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]

Hi Denis,

I ran this over the weekend and with the extra logging I can see that
ACD error is "Bad file descriptor". I captured some additional fd info
while iwd was running in the bad state and it looks like timers are
being leaked somewhere.

```
May 14 03:29:00.008410 r2-19101 iwd[477]: [DHCPv4]
announce_wait_timeout:189 Failed to send ACD announcement: Bad file
descriptor

$ cat /proc/477/limits
Limit Soft Limit Hard Limit Units
...
Max open files 1024 524288 files

$ sudo lsof -a -p 477
...
iwd 477 root 1020u a_inode 0,13 0 13445 [timerfd]
iwd 477 root 1021u a_inode 0,13 0 13445 [timerfd]
iwd 477 root 1022u a_inode 0,13 0 13445 [timerfd]
iwd 477 root 1023u a_inode 0,13 0 13445 [timerfd]
```

https://pastebin.com/BHYVTSXT

Regards,
Michael

On Fri, 13 May 2022 at 12:27, Michael Johnson <mjohnson459(a)gmail.com> wrote:
>
> Hi Denis,
>
> I've updated some of the clients in my test environment to use your
> latest ell debug logging patch and I'll let you know what error I see.
>
> On Thu, 12 May 2022 at 18:50, Denis Kenzior <denkenz(a)gmail.com> wrote:
> > > May 12 15:05:02 r2-19006 iwd[475]: [DHCPv4] announce_wait_timeout:187
> > > Failed to send ACD announcement
> > > ```
> >
> > Yes, I saw that.  Looking at the code, we should fail to start acd if we're
> > running out of fds and this logic wouldn't be triggered...
>
> I'm not sure this is related but I notice that in normal logging there
> are never any retries of this method as this is never printed:
> ```
> announce_wait_timeout: ACD_DEBUG("Done announcing");
> ```
> which makes sense as the timeout object is NULL when "skip_probes" is true.
> ```
> l_acd_start: announce_wait_timeout(NULL, acd);
> ```
>
> Regards,
> Michael

             reply	other threads:[~2022-05-16  9:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16  9:38 Michael Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-13 11:27 DHCP renewal stops after disconnect Michael Johnson
2022-05-13  9:58 Michael Johnson
2022-05-12 17:50 Denis Kenzior
2022-05-12 17:02 Michael Johnson
2022-05-12 16:37 Denis Kenzior
2022-05-12 16:19 Michael Johnson
2022-05-11 18:52 Denis Kenzior
2022-05-11 18:41 Michael Johnson
2022-05-11 18:21 Denis Kenzior
2022-05-11 18:13 Michael Johnson
2022-05-11 17:32 Denis Kenzior
2022-05-11 16:22 Michael Johnson
2022-05-11 15:56 Denis Kenzior
2022-05-11 10:53 Michael Johnson

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='CACsRnHVzAPXVDh2qSgGbpqo_yBAco+UHuehAZCouXbuVN7=zKQ@mail.gmail.com' \
    --to=unknown@example.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.