From: "Gianluca Stivan" <me@yawnt.com>
To: "Stefano Brivio" <sbrivio@redhat.com>
Cc: passt-user@passt.top
Subject: Re: Failed to open tun socket in namespace
Date: Mon, 27 Mar 2023 13:22:12 +0100 [thread overview]
Message-ID: <a66da2ba-9b0a-49f4-8ff3-604311d902d2@app.fastmail.com> (raw)
In-Reply-To: <20230327114729.4f7a5c7d@elisabeth>
Thanks for the reply!
Here is the ending of the log file:
...
<a lot a lot of STALLED and dropped...>
3944.3562: TCP: index 19, timer expires in 2.000s
3944.3563: TCP: index 19, timer expires in 2.000s
3944.3566: TCP: index 19: STALLED
3944.3578: TCP: index 7: STALLED dropped
3944.3579: TCP: index 7, timer expires in 2.000s
3944.3584: TCP: index 7: STALLED
3944.3586: TCP: index 7: STALLED dropped
3944.3587: TCP: index 7: ACK_FROM_TAP_DUE dropped
3944.3588: TCP: index 7: ACK_FROM_TAP_DUE
3944.3588: TCP: index 7, timer expires in 2.000s
3944.3589: TCP: index 12: STALLED dropped
3944.3590: TCP: index 12, timer expires in 2.000s
3944.3620: tap write: No buffer space available
3944.3620: TCP: index 17: STALLED dropped
3944.3620: TCP: index 17: ACK_FROM_TAP_DUE dropped
3944.4420: ERROR: Failed to open tun socket in namespace
No buffer space available seems interesting?
Thanks!
PS: let me know if you'd like the full file!
On Mon, Mar 27, 2023, at 10:47, Stefano Brivio wrote:
> Hi Gianluca,
>
> On Sun, 26 Mar 2023 13:42:19 +0100
> "Gianluca Stivan" <me@yawnt.com> wrote:
>
>> Hi,
>> Thank you so much for this project!
>
> And thanks for testing it!
>
>> I'm running a rootless container using pasta. Everything works great
>> but after a while (anything from minutes to hours) I see the error
>> "Failed to open tun socket in namespace" in my systemd logs, and my
>> container loses access to the internet.
>
> That happens when pasta detects an issue with the tap file descriptor
> (error or closure reported by the kernel, or failed read), so it closes
> it and tries to open it again.
>
> There are two issues actually: 1. the problem with the tap device
> causing this and 2. the fact that pasta fails to close and reopen the
> file descriptor.
>
>> Do you happen to have any
>> idea how I would go about debugging this? Thanks a lot in advance :)
>>
>> PS: I'm running pasta from podman with arguments
>> --map-gw,--dns,<my-dns>,-i,wlan0,--outbound-if4,wireguard0,--outbound-if6,wireguard0,--config-net
>
> Let's try to debug issue 1. first: can you pass -d (--debug) and -l
> (--log-file) here, then check the lines at the end, when pasta
> terminates? You might want to play with --log-size too if there's a lot
> of activity.
>
> --
> Stefano
next prev parent reply other threads:[~2023-03-27 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 12:42 Failed to open tun socket in namespace Gianluca Stivan
2023-03-27 9:47 ` Stefano Brivio
2023-03-27 12:22 ` Gianluca Stivan [this message]
2023-03-27 13:02 ` Stefano Brivio
2023-03-27 13:16 ` Gianluca Stivan
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=a66da2ba-9b0a-49f4-8ff3-604311d902d2@app.fastmail.com \
--to=me@yawnt.com \
--cc=passt-user@passt.top \
--cc=sbrivio@redhat.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 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 IMAP folder(s).