On 11/01/2021 03:25, Jerome Lille wrote:
On Sun, 2021-01-10 at 15:44 +0800, Ed Greshko wrote:
On 06/01/2021 00:10, Jerome Lille wrote:
I've just updated a desktop from Fedora 32 to 33 and after that the
logs are flooded with the following message
systemd-resolved[]: Using degraded feature set
On Sun, 2021-01-10 at 15:44 +0800, Ed Greshko wrote:
> On 06/01/2021 00:10, Jerome Lille wrote:
> > I've just updated a desktop from Fedora 32 to 33 and after that the
> > logs are flooded with the following message
> >
> > systemd-resolved[]: Using degraded feature set TCP instead of UDP
> > for
Ed Greshko writes:
Networkmanager must be checking if /etc/resolv.conf is a symbolic link and
only updating its own private resolver configs, otherwise it'll update them
and /etc/resolv.conf
I have no idea of what "private configs" you speak. I also can't think of
The configs in /var/run
On 10/01/2021 14:50, Ed Greshko wrote:
I also can't think of why NM would ever check if
/etc/resolv.conf was a symlink.
I actually meant to say there would be no need to check if systemd-resolved is
masked.
But, either way, that was not a very well thought out statement.
---
The key to gettin
On 06/01/2021 00:10, Jerome Lille wrote:
I've just updated a desktop from Fedora 32 to 33 and after that the
logs are flooded with the following message
systemd-resolved[]: Using degraded feature set TCP instead of UDP for
DNS server 127.0.0.1.
systemd-resolved[]: Using degraded feature set UDP
On 10/01/2021 11:04, Tim via users wrote:
Ed Greshko:
When I tested reverting to the previous behavior I simply started
with an empty /etc/resolv.conf.
No symlink. No selinux troubles. Everything just worked.
Sam Varshavchik:
Well, then how do the apps that need to talk to the DNS server fin
On 10/01/2021 12:24, Sam Varshavchik wrote:
Tim via users writes:
Ed Greshko:
>> When I tested reverting to the previous behavior I simply started
>> with an empty /etc/resolv.conf.
>> No symlink. No selinux troubles. Everything just worked.
Sam Varshavchik:
> Well, then how do the apps that
Tim via users writes:
Ed Greshko:
>> When I tested reverting to the previous behavior I simply started
>> with an empty /etc/resolv.conf.
>> No symlink. No selinux troubles. Everything just worked.
Sam Varshavchik:
> Well, then how do the apps that need to talk to the DNS server find
> it? M
Ed Greshko:
>> When I tested reverting to the previous behavior I simply started
>> with an empty /etc/resolv.conf.
>> No symlink. No selinux troubles. Everything just worked.
Sam Varshavchik:
> Well, then how do the apps that need to talk to the DNS server find
> it? Maybe something in the gli
Ed Greshko writes:
When I tested reverting to the previous behavior I simply started with an
empty /etc/resolv.conf.
No symlink. No selinux troubles. Everything just worked.
Well, then how do the apps that need to talk to the DNS server find it?
Maybe something in the glibc resolver know
On 10/01/2021 09:17, Ed Greshko wrote:
On 10/01/2021 09:12, Sam Varshavchik wrote:
Doug H. writes:
>
> Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to
> be fixed.
Thanks for opening that bug.
Note that my outbound e-mail was being blocked by this. I am using post
On 10/01/2021 09:12, Sam Varshavchik wrote:
Doug H. writes:
>
> Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to
> be fixed.
Thanks for opening that bug.
Note that my outbound e-mail was being blocked by this. I am using postfix for outbound and the smtp alerts
we
Doug H. writes:
>
> Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to
> be fixed.
Thanks for opening that bug.
Note that my outbound e-mail was being blocked by this. I am using postfix
for outbound and the smtp alerts were triggering for each outbound e-mail
att
On Wed, Jan 6, 2021, at 4:15 AM, Sam Varshavchik wrote:
> Jerome Lille writes:
>
> > On Tue, 2021-01-05 at 18:10 -0500, Sam Varshavchik wrote:
> > > Chris Murphy writes:
> > >
> > > > On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy
> > > > wrote:
> > > > >
> > > > > Maybe this bug:
> > > >
> > > > h
Michael H. Warfield writes:
> What I do is disable systemd-resolved and fix the resolv.conf file
> to put back the original and get rid of systemd's symlink.
ALSO! Remove the "resolve [!UNAVAIL=return]" stanza for hosts in
/etc/nsswitch.conf! That seems to have been part of my problems.
Thi
On Tue, 2021-01-05 at 11:35 -0500, Tom Horsley wrote:
> On Tue, 05 Jan 2021 17:10:06 +0100
> Jerome Lille wrote:
> > What can be done?
>
> What I do is disable systemd-resolved and fix the resolv.conf file
> to put back the original and get rid of systemd's symlink.
ALSO! Remove the "resolve [!
Jerome Lille writes:
On Tue, 2021-01-05 at 18:10 -0500, Sam Varshavchik wrote:
> Chris Murphy writes:
>
> > On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy
> > wrote:
> > >
> > > Maybe this bug:
> >
> > https://github.com/systemd/systemd/issues/13432
>
> "opened this issue on Aug 29, 2019"
>
> I w
On Tue, 2021-01-05 at 18:10 -0500, Sam Varshavchik wrote:
> Chris Murphy writes:
>
> > On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy
> > wrote:
> > >
> > > Maybe this bug:
> >
> > https://github.com/systemd/systemd/issues/13432
>
> "opened this issue on Aug 29, 2019"
>
> I would not expect thi
Chris Murphy writes:
On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy wrote:
>
> Maybe this bug:
https://github.com/systemd/systemd/issues/13432
"opened this issue on Aug 29, 2019"
I would not expect this to be fixed any time soon. The only solution is:
systemctl stop systemd-resolved
systemct
On Tue, 2021-01-05 at 10:33 -0700, Chris Murphy wrote:
> On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy
> wrote:
> >
> > On Tue, Jan 5, 2021 at 9:10 AM Jerome Lille
> > wrote:
> > >
> > > Hi
> > >
> > > I've just updated a desktop from Fedora 32 to 33 and after that
> > > the
> > > logs are floo
On Tue, 2021-01-05 at 11:37 -0500, Tim Evans wrote:
> On 1/5/21 11:10 AM, Jerome Lille wrote:
>
> > This machine uses a VPN service that is always on. The file
> > /etc/resolver.conf has just one line with the nameserver from the
> > VPN
>
> You do mean /etc/resolv.conf, right?
Right
___
On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy wrote:
>
> On Tue, Jan 5, 2021 at 9:10 AM Jerome Lille wrote:
> >
> > Hi
> >
> > I've just updated a desktop from Fedora 32 to 33 and after that the
> > logs are flooded with the following message
> >
> > systemd-resolved[]: Using degraded feature set
On Tue, Jan 5, 2021 at 9:10 AM Jerome Lille wrote:
>
> Hi
>
> I've just updated a desktop from Fedora 32 to 33 and after that the
> logs are flooded with the following message
>
> systemd-resolved[]: Using degraded feature set TCP instead of UDP for
> DNS server 127.0.0.1.
> systemd-resolved[]: Us
On 1/5/21 11:10 AM, Jerome Lille wrote:
This machine uses a VPN service that is always on. The file
/etc/resolver.conf has just one line with the nameserver from the VPN
You do mean /etc/resolv.conf, right?
--
Tim Evans | 5 Chestnut Court
On Tue, 05 Jan 2021 17:10:06 +0100
Jerome Lille wrote:
> What can be done?
What I do is disable systemd-resolved and fix the resolv.conf file
to put back the original and get rid of systemd's symlink.
___
users mailing list -- users@lists.fedoraproject.
Hi
I've just updated a desktop from Fedora 32 to 33 and after that the
logs are flooded with the following message
systemd-resolved[]: Using degraded feature set TCP instead of UDP for
DNS server 127.0.0.1.
systemd-resolved[]: Using degraded feature set UDP instead of TCP for
DNS server 127.0.0.1
26 matches
Mail list logo
