Long wait for start job

classic Classic list List threaded Threaded
99 messages Options
12345
Reply | Threaded
Open this post in threaded view
|

Long wait for start job

Frank McCormick-2
Just did a new installation of the basic fedora 34 desktop the one which
provides a bunch of basic window managers using a netinstall iso.

The boot is interrupted for a longtime (2 minutes) while
a start job runs for wait for udev to complete initialization.

The timeout is three minutes and it almost reaches that point
before continuing.

I have looked through
the syslogs but the only obvious problem is a core dump
by alsa control which I don't understand because prior to this running
Fedora 33 nothing similar happened.

Need some advice on how to debug this.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Joe Zeff
On 6/11/21 8:16 PM, Frank McCormick wrote:
>
> The boot is interrupted for a longtime (2 minutes) while
> a start job runs for wait for udev to complete initialization.
>
> The timeout is three minutes and it almost reaches that point
> before continuing.

Run systemd-analyze blame and take a look at the first items listed.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Patrick O'Callaghan
On Fri, 2021-06-11 at 20:26 -0600, Joe Zeff wrote:
> On 6/11/21 8:16 PM, Frank McCormick wrote:
> >
> > The boot is interrupted for a longtime (2 minutes) while
> > a start job runs for wait for udev to complete initialization.
> >
> > The timeout is three minutes and it almost reaches that point
> > before continuing.
>
> Run systemd-analyze blame and take a look at the first items listed.

I don't want to hijack Frank's thread, but I have a similar situation,
apparently caused by a very slow initialization of an external USB
drive. However the drive is not automatically mounted (it's controlled
by an automount) so I don't see why the system needs to wait for it.

I've posted the output of "systemd-analyse plot" if anyone one to take
a look. The culprit is obvious at a glance. The only thing special
about this device is that it's an external dock with two disks
configured as a BTRFS RAID1.

See https://paste.centos.org/view/7f4216fa

poc
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Frank McCormick-2
In reply to this post by Joe Zeff
Systemd-analyze blame pinpoints "systemd-udev-settle.service" more than
a 2 minute wait!!


_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Chris Murphy
Both problems need logs. It's quite a bit over kill but these boot parameters will help provide enough info.

systemd.log_level=debug udev.log-priority=​debug rd.debug x-systemd.timeout=180

The debug options are resource inventive and slow down boot by allot. The point of the timeout is hopefully avoiding the dracut shell. But better to get the shell than an indefinite hang. 

journalctl -b -o short-monotonic --no-hostname > journal.log

Copy that out to a file sharing service, and post the URL.

Chris Murphy

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Frank McCormick-2
I found and fixed the problem. The key was in my systemd log.

  1.825245] udevadm[363]: systemd-udev-settle.service is deprecated.
Please fix nm-initrd.service not to pull it in


Personally I think this should be spread more...it seems there are quite
a few with this problem
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Greg Woods-2


On Sat, Jun 12, 2021 at 9:32 AM Frank McCormick <[hidden email]> wrote:
I found and fixed the problem. The key was in my systemd log.

  1.825245] udevadm[363]: systemd-udev-settle.service is deprecated.
Please fix nm-initrd.service not to pull it in

Interesting; on my F34 system, the message mentions nm-run.service rather than nm-initrd.service. Neither nm-run nor nm-initrd exist as services, but something is calling systemd-udev-settle although it only takes 2 seconds to run and exit, so I never noticed this before.

--Greg
 

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Joe Zeff
In reply to this post by Frank McCormick-2
On 6/12/21 6:32 AM, Frank McCormick wrote:
> Systemd-analyze blame pinpoints "systemd-udev-settle.service" more than
> a 2 minute wait!!

According to https://github.com/openzfs/zfs/issues/10891 has been
depricated since last year.  Disable and mask it and that should fix
your issue.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Tom Horsley
On Sat, 12 Jun 2021 10:44:19 -0600
Joe Zeff wrote:

> According to https://github.com/openzfs/zfs/issues/10891 has been
> depricated since last year.  Disable and mask it and that should fix
> your issue.

It is listed as a "static" service on my system. Can those be
disabled or masked?
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Patrick O'Callaghan
In reply to this post by Chris Murphy
On Sat, 2021-06-12 at 07:25 -0600, Chris Murphy wrote:

> Both problems need logs. It's quite a bit over kill but these boot
> parameters will help provide enough info.
>
> systemd.log_level=debug udev.log-priority=​debug
> rd.debug x-systemd.timeout=180
>
> The debug options are resource inventive and slow down boot by allot.
> The
> point of the timeout is hopefully avoiding the dracut shell. But better
> to
> get the shell than an indefinite hang.
>
> journalctl -b -o short-monotonic --no-hostname > journal.log
>
> Copy that out to a file sharing service, and post the URL.

https://paste.centos.org/view/3932b04e

poc
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Patrick O'Callaghan
In reply to this post by Frank McCormick-2
On Sat, 2021-06-12 at 11:31 -0400, Frank McCormick wrote:
> I found and fixed the problem. The key was in my systemd log.
>
>   1.825245] udevadm[363]: systemd-udev-settle.service is deprecated.
> Please fix nm-initrd.service not to pull it in
>
>
> Personally I think this should be spread more...it seems there are
> quite
> a few with this problem

Not my case. I don't have systemd-udev-settle.service. This is a fresh
install of F34.

poc
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Patrick O'Callaghan
On Sat, 2021-06-12 at 18:54 +0100, Patrick O'Callaghan wrote:

> On Sat, 2021-06-12 at 11:31 -0400, Frank McCormick wrote:
> > I found and fixed the problem. The key was in my systemd log.
> >
> >   1.825245] udevadm[363]: systemd-udev-settle.service is deprecated.
> > Please fix nm-initrd.service not to pull it in
> >
> >
> > Personally I think this should be spread more...it seems there are
> > quite
> > a few with this problem
>
> Not my case. I don't have systemd-udev-settle.service. This is a fresh
> install of F34.

I spoke too soon. A grep on the journal log (posted earlier) shows:

$ grep settle journal.log
[    1.763070] udevadm[412]: systemd-udev-settle.service is deprecated. Please fix nm-initrd.service not to pull it in.
[   32.655548] systemd[1]: systemd-udev-settle.service: Deactivated successfully.
[   34.383171] udevadm[626]: systemd-udev-settle.service is deprecated. Please fix multipathd.service not to pull it in.

I have no idea what this means. What does NM have to do with anything
and how do I "fix" it? I also don't have an /etc/multipath.conf file.
Could that be the problem?

poc

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Joe Zeff
In reply to this post by Patrick O'Callaghan
On 6/12/21 11:54 AM, Patrick O'Callaghan wrote:
> Not my case. I don't have systemd-udev-settle.service. This is a fresh
> install of F34.

Ok, you can still use systemd-analyze blame to find out what's causing
the delay.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Samuel Sieb
In reply to this post by Tom Horsley
On 2021-06-12 10:19 a.m., Tom Horsley wrote:
> On Sat, 12 Jun 2021 10:44:19 -0600
> Joe Zeff wrote:
>
>> According to https://github.com/openzfs/zfs/issues/10891 has been
>> depricated since last year.  Disable and mask it and that should fix
>> your issue.
>
> It is listed as a "static" service on my system. Can those be
> disabled or masked?

It can't be disabled, but it can be masked.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Patrick O'Callaghan
On Sat, 2021-06-12 at 14:43 -0700, Samuel Sieb wrote:

> On 2021-06-12 10:19 a.m., Tom Horsley wrote:
> > On Sat, 12 Jun 2021 10:44:19 -0600
> > Joe Zeff wrote:
> >
> > > According to https://github.com/openzfs/zfs/issues/10891 has been
> > > depricated since last year.  Disable and mask it and that should
> > > fix
> > > your issue.
> >
> > It is listed as a "static" service on my system. Can those be
> > disabled or masked?
>
> It can't be disabled, but it can be masked.

I've masked it and rebooted. Makes no difference to boot time in my
case.

$ systemctl status systemd-udev-settle.service
○ systemd-udev-settle.service
     Loaded: masked (Reason: Unit systemd-udev-settle.service is masked.)
     Active: inactive (dead) since Sun 2021-06-13 00:14:30 BST; 29min left
   Main PID: 413 (code=exited, status=0/SUCCESS)
        CPU: 0

Jun 13 00:13:59 Bree systemd[1]: Starting Wait for udev To Complete Device Initialization...
Jun 13 00:13:59 Bree udevadm[413]: systemd-udev-settle.service is deprecated. Please fix nm-initrd.service not to pull it in.
Jun 13 00:14:29 Bree systemd[1]: Finished Wait for udev To Complete Device Initialization.
Jun 13 00:14:30 Bree systemd[1]: systemd-udev-settle.service: Deactivated successfully.
Jun 13 00:14:30 Bree systemd[1]: Stopped Wait for udev To Complete Device Initialization.

poc
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Ed Greshko
On 13/06/2021 06:46, Patrick O'Callaghan wrote:

> On Sat, 2021-06-12 at 14:43 -0700, Samuel Sieb wrote:
>> On 2021-06-12 10:19 a.m., Tom Horsley wrote:
>>> On Sat, 12 Jun 2021 10:44:19 -0600
>>> Joe Zeff wrote:
>>>
>>>> According to https://github.com/openzfs/zfs/issues/10891 has been
>>>> depricated since last year.  Disable and mask it and that should
>>>> fix
>>>> your issue.
>>> It is listed as a "static" service on my system. Can those be
>>> disabled or masked?
>> It can't be disabled, but it can be masked.
> I've masked it and rebooted. Makes no difference to boot time in my
> case.
>
> $ systemctl status systemd-udev-settle.service
> ○ systemd-udev-settle.service
>       Loaded: masked (Reason: Unit systemd-udev-settle.service is masked.)
>       Active: inactive (dead) since Sun 2021-06-13 00:14:30 BST; 29min left
>     Main PID: 413 (code=exited, status=0/SUCCESS)
>          CPU: 0
>
> Jun 13 00:13:59 Bree systemd[1]: Starting Wait for udev To Complete Device Initialization...
> Jun 13 00:13:59 Bree udevadm[413]: systemd-udev-settle.service is deprecated. Please fix nm-initrd.service not to pull it in.
> Jun 13 00:14:29 Bree systemd[1]: Finished Wait for udev To Complete Device Initialization.
> Jun 13 00:14:30 Bree systemd[1]: systemd-udev-settle.service: Deactivated successfully.
> Jun 13 00:14:30 Bree systemd[1]: Stopped Wait for udev To Complete Device Initialization.
>

But, does your plot show a difference?

--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Samuel Sieb
In reply to this post by Patrick O'Callaghan
On 2021-06-12 3:46 p.m., Patrick O'Callaghan wrote:

> On Sat, 2021-06-12 at 14:43 -0700, Samuel Sieb wrote:
>> On 2021-06-12 10:19 a.m., Tom Horsley wrote:
>>> On Sat, 12 Jun 2021 10:44:19 -0600
>>> Joe Zeff wrote:
>>>
>>>> According to https://github.com/openzfs/zfs/issues/10891 has been
>>>> depricated since last year.  Disable and mask it and that should
>>>> fix
>>>> your issue.
>>>
>>> It is listed as a "static" service on my system. Can those be
>>> disabled or masked?
>>
>> It can't be disabled, but it can be masked.
>
> I've masked it and rebooted. Makes no difference to boot time in my
> case.
>
> Jun 13 00:13:59 Bree systemd[1]: Starting Wait for udev To Complete Device Initialization...
> Jun 13 00:13:59 Bree udevadm[413]: systemd-udev-settle.service is deprecated. Please fix nm-initrd.service not to pull it in.
> Jun 13 00:14:29 Bree systemd[1]: Finished Wait for udev To Complete Device Initialization.
> Jun 13 00:14:30 Bree systemd[1]: systemd-udev-settle.service: Deactivated successfully.
> Jun 13 00:14:30 Bree systemd[1]: Stopped Wait for udev To Complete Device Initialization.

That is weird.  It shouldn't get run if it's masked.  Is the service
file in /etc/systemd/system by any chance?
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Ed Greshko
In reply to this post by Ed Greshko
On 13/06/2021 06:57, Ed Greshko wrote:
> But, does your plot show a difference?

Speaking of your plot.....

Don't you think the time between

sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.6-1\x2d1.6.2.device and
dev-disk-by\x2dpath-pci\x2d0000:00:14.0\x2dusb\x2d0:3:1.0\x2dscsi\x2d0:0:0:1.device

worth looking into?

--
Remind me to ignore comments which aren't germane to the thread.

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Ed Greshko
In reply to this post by Samuel Sieb
On 13/06/2021 07:06, Samuel Sieb wrote:

> On 2021-06-12 3:46 p.m., Patrick O'Callaghan wrote:
>> On Sat, 2021-06-12 at 14:43 -0700, Samuel Sieb wrote:
>>> On 2021-06-12 10:19 a.m., Tom Horsley wrote:
>>>> On Sat, 12 Jun 2021 10:44:19 -0600
>>>> Joe Zeff wrote:
>>>>
>>>>> According to https://github.com/openzfs/zfs/issues/10891 has been
>>>>> depricated since last year.  Disable and mask it and that should
>>>>> fix
>>>>> your issue.
>>>>
>>>> It is listed as a "static" service on my system. Can those be
>>>> disabled or masked?
>>>
>>> It can't be disabled, but it can be masked.
>>
>> I've masked it and rebooted. Makes no difference to boot time in my
>> case.
>>
>> Jun 13 00:13:59 Bree systemd[1]: Starting Wait for udev To Complete Device Initialization...
>> Jun 13 00:13:59 Bree udevadm[413]: systemd-udev-settle.service is deprecated. Please fix nm-initrd.service not to pull it in.
>> Jun 13 00:14:29 Bree systemd[1]: Finished Wait for udev To Complete Device Initialization.
>> Jun 13 00:14:30 Bree systemd[1]: systemd-udev-settle.service: Deactivated successfully.
>> Jun 13 00:14:30 Bree systemd[1]: Stopped Wait for udev To Complete Device Initialization.
>
> That is weird.  It shouldn't get run if it's masked.  Is the service file in /etc/systemd/system by any chance?

Since it is being "pulled in" by other services I think you may expect to see this.

FWIW, I masked that service and it still shows up in systemd-analyse but the times have changed from
several seconds (I think it was 6ish) to 542ms.

--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Reply | Threaded
Open this post in threaded view
|

Re: Long wait for start job

Samuel Sieb
On 2021-06-12 4:14 p.m., Ed Greshko wrote:

> On 13/06/2021 07:06, Samuel Sieb wrote:
>> On 2021-06-12 3:46 p.m., Patrick O'Callaghan wrote:
>>> On Sat, 2021-06-12 at 14:43 -0700, Samuel Sieb wrote:
>>>> On 2021-06-12 10:19 a.m., Tom Horsley wrote:
>>>>> On Sat, 12 Jun 2021 10:44:19 -0600
>>>>> Joe Zeff wrote:
>>>>>
>>>>>> According to https://github.com/openzfs/zfs/issues/10891 has been
>>>>>> depricated since last year.  Disable and mask it and that should
>>>>>> fix
>>>>>> your issue.
>>>>>
>>>>> It is listed as a "static" service on my system. Can those be
>>>>> disabled or masked?
>>>>
>>>> It can't be disabled, but it can be masked.
>>>
>>> I've masked it and rebooted. Makes no difference to boot time in my
>>> case.
>>>
>>> Jun 13 00:13:59 Bree systemd[1]: Starting Wait for udev To Complete
>>> Device Initialization...
>>> Jun 13 00:13:59 Bree udevadm[413]: systemd-udev-settle.service is
>>> deprecated. Please fix nm-initrd.service not to pull it in.
>>> Jun 13 00:14:29 Bree systemd[1]: Finished Wait for udev To Complete
>>> Device Initialization.
>>> Jun 13 00:14:30 Bree systemd[1]: systemd-udev-settle.service:
>>> Deactivated successfully.
>>> Jun 13 00:14:30 Bree systemd[1]: Stopped Wait for udev To Complete
>>> Device Initialization.
>>
>> That is weird.  It shouldn't get run if it's masked.  Is the service
>> file in /etc/systemd/system by any chance?
>
> Since it is being "pulled in" by other services I think you may expect
> to see this.

 From the systemctl man page describing the "mask" command:
Mask one or more units, as specified on the command line. This will link
these unit files to /dev/null, making it impossible to start them. This
is a stronger version of disable, since it prohibits all kinds of
activation of the unit, including enablement and manual activation.

"impossible to start them" and "prohibits all kinds of activation of the
unit"

And from the description of what the "masked" status means:
Completely disabled, so that any start operation on it fails.

But as shown from the quoted log lines, "udevadm" is definitely getting
called still.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
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@...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
12345