Re: Network: Limited Connectivity since upgrade to Fedora 39

2023-12-29 Thread Samuel Sieb 

On 12/29/23 13:05, Tim via users wrote:

On Fri, 2023-12-29 at 11:48 -0500, Jeffrey Walton wrote:

There are usually lots of dangling symlinks, so you may want to clean
up the dangling links.


This kind of thing (lots of annoying post-install fix-ups) is why I
gave up doing upgrades, many years ago.


I have done probably over a hundred upgrades of systems without problems 
and no post-install fixups.



I do fresh installs, where the only thing I know I have to do is
configure the services I want to run.  It's far less mental gymnastics
of trying to figure out what got mangled, and takes me less time to do.


A fresh install would cause me so much trouble.  I have installed 
packages and settings over time and I would hate to have to redo all 
that each time, after figuring out what I've done in the first place.

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Network: Limited Connectivity since upgrade to Fedora 39

2023-12-29 Thread Barry 


> On 29 Dec 2023, at 21:06, Tim via users  wrote:
> 
> This kind of thing (lots of annoying post-install fix-ups) is why I
> gave up doing upgrades, many years ago.

I have non trivia configuration that a fresh install will force me to apply 
again and again.
At home I have fedora running on multiple machines, routers, file, web and imsp 
servers as well as development desktops. Also a lot other VMs.

But I do keep all config and custom scripts in source control against the day I 
have to fresh install.

> 
> I do fresh installs, where the only thing I know I have to do is
> configure the services I want to run.  It's far less mental gymnastics
> of trying to figure out what got mangled, and takes me less time to do.

I only even fresh install when I have new hardware.

My experience is that few things break on updates or upgrades.
Those breaks are not that hard to fix.

Barry

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Network: Limited Connectivity since upgrade to Fedora 39

2023-12-29 Thread Tim via users 
On Fri, 2023-12-29 at 11:48 -0500, Jeffrey Walton wrote:
> There are usually lots of dangling symlinks, so you may want to clean
> up the dangling links.

This kind of thing (lots of annoying post-install fix-ups) is why I
gave up doing upgrades, many years ago.

I do fresh installs, where the only thing I know I have to do is
configure the services I want to run.  It's far less mental gymnastics
of trying to figure out what got mangled, and takes me less time to do.

Not to mention that the post-upgrade help guides only document things
that people have discovered.  You may well have things they don't know
about to fix up.
 
-- 
 
NB:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the list.
 
The following system info data is generated fresh for each post:
 
uname -rsvp
Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53
UTC 2023 x86_64
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Network: Limited Connectivity since upgrade to Fedora 39

2023-12-29 Thread Klaus-Peter Schrage via users 

Am 29.12.23 um 17:48 schrieb Jeffrey Walton:



But an issue remains: Why got mysystem mal-labelled? I didn't do many things to 
it after the upgrade,
and shouldn't be labelling be part of the system-upgrade process?
But thanks again for your help.

There are several post-upgrade steps that may be useful to you:

and 
.
There are usually lots of dangling symlinks, so you may want to clean
up the dangling links.

Since relabeling is under the section "Resolving post-upgrade issues,"
I'm guessing relabeling does not occur as part of the upgrade process.

Jeff

Thanks Jeff, I knew about these docs, and I usually follow some of post
upgrade steps, but I missed relabelling, which I will never forget again!
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Network: Limited Connectivity since upgrade to Fedora 39

2023-12-29 Thread Jeffrey Walton 
On Fri, Dec 29, 2023 at 11:40 AM Klaus-Peter Schrage via users
 wrote:
>
> Am 29.12.23 um 16:36 schrieb Barry Scott:
> >> On 29 Dec 2023, at 11:12, Klaus-Peter Schrage via users 
> >>  wrote:
> >> [...]
> > That is very odd. | have seen a number of people seeing odd things failing
> > as a result of selinux labelling errors. You could try to the auto 
> > relabelling and
> > see if that fixes it.
> >
> > touch /.autorelabel
> > reboot
> > [...]
> >
> Thanks, Barry, you were right in suspecting selinux: After
> autorelabelling, I booted the system for several times without the
> problem ever reoccurring. So for me, there is sufficient statistical
> evidence that my problem is solved. But an issue remains: Why got my
> system mal-labelled? I didn't do many things to it after the upgrade,
> and shouldn't be labelling be part of the system-upgrade process?
> But thanks again for your help.

There are several post-upgrade steps that may be useful to you:

and 
.
There are usually lots of dangling symlinks, so you may want to clean
up the dangling links.

Since relabeling is under the section "Resolving post-upgrade issues,"
I'm guessing relabeling does not occur as part of the upgrade process.

Jeff
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Network: Limited Connectivity since upgrade to Fedora 39

2023-12-29 Thread Klaus-Peter Schrage via users 

Am 29.12.23 um 16:36 schrieb Barry Scott:

On 29 Dec 2023, at 11:12, Klaus-Peter Schrage via users 
 wrote:

Recently, I did an upgrade to F39 via dnf system-upgrade. For the first
time in Fedora (I think I started around version 1), on booting into KDE
I get a message saying "limited network connectivity", which means, my
wired network is up but can't reach the outside world.

The journals tell me that the name resolution is not working (see
attached log). I didn't find out why it failed, but restarting
systemd-resolved usually cures the problem. The problem that the service
fails on startup still remains, but not on every boot. Sometimes, say in
10 % of bootings, the problem doesn't occur.
If those things matter:
- Desktop computer with KDE-Plasma (X11)
- kernel 6.6.8-200.fc39.x86_64
- NIC: Intel 82574L with kernel driver e1000e

I have the faint idea thast there might be a race condition between
services on startup,
Any pointers to debug that further would be welcome.
--

That is very odd. | have seen a number of people seeing odd things failing
as a result of selinux labelling errors. You could try to the auto relabelling 
and
see if that fixes it.

touch /.autorelabel
reboot

Other then that you could try running /usr/lib/systemd/systemd-resolved as root
in debug mode and see if reports any errors.

systemctl stop systemd-resolved
SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-resolved


Thanks, Barry, you were right in suspecting selinux: After
autorelabelling, I booted the system for several times without the
problem ever reoccurring. So for me, there is sufficient statistical
evidence that my problem is solved. But an issue remains: Why got my
system mal-labelled? I didn't do many things to it after the upgrade,
and shouldn't be labelling be part of the system-upgrade process?
But thanks again for your help.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Network: Limited Connectivity since upgrade to Fedora 39

2023-12-29 Thread Barry Scott 


> On 29 Dec 2023, at 11:12, Klaus-Peter Schrage via users 
>  wrote:
> 
> Recently, I did an upgrade to F39 via dnf system-upgrade. For the first
> time in Fedora (I think I started around version 1), on booting into KDE
> I get a message saying "limited network connectivity", which means, my
> wired network is up but can't reach the outside world.
> 
> The journals tell me that the name resolution is not working (see
> attached log). I didn't find out why it failed, but restarting
> systemd-resolved usually cures the problem. The problem that the service
> fails on startup still remains, but not on every boot. Sometimes, say in
> 10 % of bootings, the problem doesn't occur.
> If those things matter:
> - Desktop computer with KDE-Plasma (X11)
> - kernel 6.6.8-200.fc39.x86_64
> - NIC: Intel 82574L with kernel driver e1000e
> 
> I have the faint idea thast there might be a race condition between
> services on startup,
> Any pointers to debug that further would be welcome.
> --

That is very odd. | have seen a number of people seeing odd things failing
as a result of selinux labelling errors. You could try to the auto relabelling 
and
see if that fixes it.

touch /.autorelabel
reboot

Other then that you could try running /usr/lib/systemd/systemd-resolved as root
in debug mode and see if reports any errors.

systemctl stop systemd-resolved
SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-resolved

Barry



> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Network: Limited Connectivity since upgrade to Fedora 39

2023-12-29 Thread Klaus-Peter Schrage via users 

Recently, I did an upgrade to F39 via dnf system-upgrade. For the first
time in Fedora (I think I started around version 1), on booting into KDE
I get a message saying "limited network connectivity", which means, my
wired network is up but can't reach the outside world.

The journals tell me that the name resolution is not working (see
attached log). I didn't find out why it failed, but restarting
systemd-resolved usually cures the problem. The problem that the service
fails on startup still remains, but not on every boot. Sometimes, say in
10 % of bootings, the problem doesn't occur.
If those things matter:
- Desktop computer with KDE-Plasma (X11)
- kernel 6.6.8-200.fc39.x86_64
- NIC: Intel 82574L with kernel driver e1000e

I have the faint idea thast there might be a race condition between
services on startup,
Any pointers to debug that further would be welcome.
░ 
░░ The unit systemd-resolved.service has entered the 'failed' state with result 'exit-code'.
Dez 29 11:55:57 localhost.localdomain systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
░░ Subject: A start job for unit systemd-resolved.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-resolved.service has finished with a failure.
░░ 
░░ The job identifier is 799 and the job result is failed.
Dez 29 11:56:04 localhost.localdomain systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Dez 29 11:56:04 localhost.localdomain systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-resolved.service has entered the 'failed' state with result 'exit-code'.
Dez 29 11:56:04 localhost.localdomain systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
░░ Subject: A start job for unit systemd-resolved.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-resolved.service has finished with a failure.
░░ 
░░ The job identifier is 2110 and the job result is failed.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue