From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>,
"dani@lapiole.org" <dani@lapiole.org>
Subject: Re: [PVE-User] PVE 8 on Bookworm, ifupdown2 fails
Date: Mon, 26 Jun 2023 09:20:28 +0000 [thread overview]
Message-ID: <3f47848c670a53536af4600e108bb0770212fb97.camel@groupe-cyllene.com> (raw)
In-Reply-To: <8c69d5119b6b29d1d6cb6fe04155dcbb39e75306.camel@groupe-cyllene.com>
ok, was able to reproduce with a segfaulting script
this patch should fix it:
https://github.com/CumulusNetworks/ifupdown2/pull/267/files
adding import traceback in /usr/share/ifupdown2/ifupdown/scheduler.py
Le lundi 26 juin 2023 à 08:51 +0000, DERUMIER, Alexandre a écrit :
> yep, proxmox don't use systemd-resolvd.
>
> But I think the traceback is a bug in ifupdown2.
>
> It's used to log debug info, but maybe the module is not yet loaded
> when the scripts in /etc/network/if-up.d/ are exec.
>
> I think I have seen a report about traceback on the forum some days
> ago.
>
> I'll try to reproduce on my side, maybe if the traceback is fixed,
> ifupdown2 will simply skip the error and continue.
>
>
> Thanks for the report !
>
>
> Le lundi 26 juin 2023 à 10:47 +0200, Daniel Berteaud a écrit :
> >
> >
> > ----- Le 26 Juin 23, à 10:45, DERUMIER, Alexandre
> > alexandre.derumier@groupe-cyllene.com a écrit :
> >
> > > debug: lo: up : running script /etc/network/if-up.d/resolved
> > > info: executing /etc/network/if-up.d/resolved
> > > error: name 'traceback' is not defined
> > >
> > > mmm, it seem to have because of this script "/etc/network/if-
> > > up.d/resolved"
> > >
> > >
> > > not sure, do you use systemd-resolvd or something like that ?
> > >
> > >
> > > can you try to remove it ? (and before, can you send the content
> > > of
> > > this file ?)
> >
> > Well, I just saw that systemd-resolved was enabled. Disabling it
> > fixed the issue. Thanks for pointing me in the right direction :-)
> > Attached is the resolved script
> >
> > Cheers,
> > Daniel
> >
> >
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2023-06-26 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.75.1687767907.232.pve-user@lists.proxmox.com>
2023-06-26 8:32 ` DERUMIER, Alexandre
2023-06-26 8:34 ` DERUMIER, Alexandre
[not found] ` <mailman.78.1687768939.232.pve-user@lists.proxmox.com>
2023-06-26 8:45 ` DERUMIER, Alexandre
[not found] ` <2051887193.15675.1687769253403.JavaMail.zimbra@lapiole.org>
2023-06-26 8:51 ` DERUMIER, Alexandre
2023-06-26 9:20 ` DERUMIER, Alexandre [this message]
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=3f47848c670a53536af4600e108bb0770212fb97.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=dani@lapiole.org \
--cc=pve-user@lists.proxmox.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