Hi. Lately I am having a couple of problems with systemd. I am using
version 250.5-r1.

I have one service which always times out, but slows down the boot
process. It is
/lib/systemd/system/systemd-networkd-wait-online.service. Because
many jobs wait in queue for a while, till this fails.

Also, I have a couple of services, ntpdate and proftpd which always
fail because when they try to execute named has not started yet. I
can restart them once the system is fully booted and I can login.

So, I wonder if this is all related to the failing service, or are
they separate problems that I can fix? And can you suggest how to fix
the two service which seem to start too soon?

Thanks in advance for any suggestions.

--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?

John Covici wb2una
[email protected]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 27 May 2022 17:03:29 -0400, John Covici wrote:

I have one service which always times out, but slows down the boot
process. It is
/lib/systemd/system/systemd-networkd-wait-online.service. Because
many jobs wait in queue for a while, till this fails.

Are you using systemd-networkd or something else to manage your network?

Also, I have a couple of services, ntpdate and proftpd which always
fail because when they try to execute named has not started yet. I
can restart them once the system is fully booted and I can login.

You can create a drop-in to require the service to start after named, run "systemctl edit ntpdate.service" and add

[Unit]
Requires=named.service
After=named.service

That will create a drop-in file in /etc/systemd/system/ntpdate.service.d containing your additions - you can also create these files manually.


--
Neil Bothwick

Copy from another: plagiarism. Copy from many: research.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmKRR2QACgkQ92eFu0QS MJi2xRAAvlI8kwEuY9Jce6zMHaF9sVa4y/hYVRKMbkd7nQMxbd3c4jII6oR/6OxL UgurN9NjxxmEGTYLTJVWAWxGZVX0VMK4wcnH59JJRnQht5lePvPon9Kv+Yy5DcOb BWAytP+EA6RXbYhbcBIacF+jc2fIRMW9Mg3jqiWE6eCGwBOD71ps27JYJz6JDsEL IjTDHO0d/48suS0MYUdgZ6NpFJv+97Fax30pv4rEhV/7rZ+WlMfehoxvLDZU1hub 1kxMJYjQfGavpfIPYZjjgbPnPRZX8jkhlstvDo7yd8x7l3bAc4YzQhj4bsU0krtg 58ZA0DplnNRs50CwpYijP6puI3shqF4PVAmVAPc5+RUW6Cf1KgeFHoV1kPazEsNT N7H3L7Vagvn1+kDABkhBedfqLujcT0emC9uhIuqa9U4/18e1O+uXLMkQPKNiEIMG 0kzV+NSa+aky0PQCnzsRyOUMKTxqRUVJpV+oZpPst6LDgPAcFtv6aSusUnIvm10R y6A0j5zskT36zQkSodR5kvmAtYARiLMK6gbX6mw7ht+kHrpJ+DrSlKvcA8E+Bzxk 3TRiY0DknMiVVW+WmcH8OxF0AMHd+zTETOUVfwNTCLr7nkfj5fpMfrl79xsgFWM0 vt7FAAt0OQ2Mk1nzCJARPmElhyAfzyGPHN9visbWaZqyCMfvBEg=
=HPq8
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 27 May 2022 17:49:24 -0400,
Neil Bothwick wrote:

[1 <text/plain; US-ASCII (quoted-printable)>]
On Fri, 27 May 2022 17:03:29 -0400, John Covici wrote:

I have one service which always times out, but slows down the boot
process. It is
/lib/systemd/system/systemd-networkd-wait-online.service. Because
many jobs wait in queue for a while, till this fails.

Are you using systemd-networkd or something else to manage your network?

Also, I have a couple of services, ntpdate and proftpd which always
fail because when they try to execute named has not started yet. I
can restart them once the system is fully booted and I can login.

You can create a drop-in to require the service to start after named, run "systemctl edit ntpdate.service" and add

[Unit]
Requires=named.service
After=named.service

That will create a drop-in file in /etc/systemd/system/ntpdate.service.d containing your additions - you can also create these files manually.

Thanks. I am not using systemd-network or anything like that. I
created a service called network and use the %i and links in /etc/systemd/system/multi-user-target.wants to start my two cards.
Maybe this is not the normal way, but when I first started using
systemd, this is the best I could come up with at the time.

I will try the drop-in, I had kind of forgot about them.


--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?

John Covici wb2una
[email protected]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 27 May 2022 19:51:06 -0400, John Covici wrote:

On Fri, 27 May 2022 17:49:24 -0400,
Neil Bothwick wrote:

[1 <text/plain; US-ASCII (quoted-printable)>]
On Fri, 27 May 2022 17:03:29 -0400, John Covici wrote:

I have one service which always times out, but slows down the boot process. It is
/lib/systemd/system/systemd-networkd-wait-online.service. Because
many jobs wait in queue for a while, till this fails.

Are you using systemd-networkd or something else to manage your
network?

Also, I have a couple of services, ntpdate and proftpd which always
fail because when they try to execute named has not started yet. I
can restart them once the system is fully booted and I can login.

You can create a drop-in to require the service to start after named,
run "systemctl edit ntpdate.service" and add

[Unit]
Requires=named.service
After=named.service

That will create a drop-in file in
/etc/systemd/system/ntpdate.service.d containing your additions - you
can also create these files manually.

Thanks. I am not using systemd-network or anything like that. I created a service called network and use the %i and links in /etc/systemd/system/multi-user-target.wants to start my two cards.
Maybe this is not the normal way, but when I first started using
systemd, this is the best I could come up with at the time.

If you are not starting systemd-networkd, network-online will fail. You
only need to create a file in /etc/systemd/network to configure your
card, something like

[Match]
Name=eth0

[Network]
Description=Wired network
DHCP=yes

Then start systemd-networkd.service.

I will try the drop-in, I had kind of forgot about them.

--
Neil Bothwick

The cow is nothing but a machine that makes grass fit for us people to
eat.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmKRyoAACgkQ92eFu0QS MJj9ghAAnLkWusmNf8yoYHEUSNE9ckk//hSRCBHYgyY6s0sVf0b4RXf+brYZAcNt x38Empz+jed3Psey6tdrE9Dm/urmOiYJt+CXmYYmIkdHGrcUtHKVlex0fX0s/Lr3 AELtMOZ3Hpuk8Q1RHQEUd07avYs6b+fjVLEoSfsAmf41/qvDnCbDkes2HwF99+wm KZounBnvBPADSqD2mla7N+sJq7iKF2dHe3M4HVvd8rUoKWWT/M/II0r3q2HgRUzA uM0qE+4Vc7SWKhFvgALgXgc5ihu683ns6R5jVJRwscZs5NNCIaMfe7Rv64sPdswc xWvdcH15mGfhOBI2w/pfZxYL0vEbBW+pwsfDXBVy5ul8B2m0j8CKxrzaXaYadDXi QBZ1m9bP5tTv4xjbB9q0C6wK/HEJqdmcW2JPKDYr9P1shll8k3ulfszL8QReFX6C SM2T1uE791Ln2akeFiVttYRwWnXZakdsSfAPGhtirluG3mWtWD1lfNDQyZ566BSg JNkPOEfRecTPUypn5x8u06zXols6HdQajo+5r62lAvCFKp+Aa26icnih4Ik5Bta9 4ChZRXvVQEGbUVHxRATN6BMVqKRaxZf3shDlqpIUHrYka6j41wnAvJm1o78WJ51d fLd9zWxKIaN06MLwoLFCsYldnxL2wUkQEx0/6sWPz5LvMlDzqq8=
=AGDo
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, May 27, 2022 at 6:51 PM John Covici <[email protected]> wrote:

[...]
Thanks. I am not using systemd-network or anything like that. I created a service called network and use the %i and links in /etc/systemd/system/multi-user-target.wants to start my two cards.
Maybe this is not the normal way, but when I first started using
systemd, this is the best I could come up with at the time.

Have you tried using .network files? You can setup it static:

$ cat /etc/systemd/network/enp2s0.network
# Ethernet

[Match]
Name=enp2s0

[Network]
Address=192.168.1.1/24
Gateway=192.168.1.254
DNS=192.168.1.254

or with DHCP:

# /etc/systemd/network/30-bond1.network
[Match]
Name=bond1

[Network]
DHCP=ipv6

Even with wpa_supplicant[1].

Regards.
[1] https://wiki.somlabs.com/index.php/Connecting_to_WiFi_network_using_systemd_and_wpa-supplicant
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México

<div dir="ltr"><div dir="ltr">On Fri, May 27, 2022 at 6:51 PM John Covici &lt;<a href="mailto:[email protected]" target="_blank">[email protected]</a>&gt; wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">[...]<br>
Thanks.  I am not using    systemd-network or anything like that.    I<br> created a service called network and use the %i and links in<br> /etc/systemd/system/multi-user-target.wants to start my two cards.<br>
Maybe this is not the normal way, but when I first started using<br>
systemd, this is the best I could come up with at the time.<br></blockquote><div><br></div><div>Have you tried using .network files? You can setup it static:</div><div><br></div><div>$ cat /etc/systemd/network/enp2s0.network <br># Ethernet<br><br>[Match]<

Name=enp2s0<br><br>[Network]<br>Address=<a href="http://192.168.1.1/24" target="_blank">192.168.1.1/24</a><br>Gateway=192.168.1.254<br>DNS=192.168.1.254<br></div><div><br></div><div>or with DHCP:</div><div><br></div><div># /etc/systemd/network/30-

bond1.network<br>[Match]<br>Name=bond1<br><br>[Network]<br>DHCP=ipv6<br></div><div><br></div><div>Even with wpa_supplicant[1].</div><div><br></div><div>Regards.</div><div>[1] <a href="https://wiki.somlabs.com/index.php/Connecting_to_WiFi_network_using_
systemd_and_wpa-supplicant">https://wiki.somlabs.com/index.php/Connecting_to_WiFi_network_using_systemd_and_wpa-supplicant</a></div><div>--<br></div></div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><font face="arial, helvetica, sans-serif">Dr.
Canek Peláez Valdés<br>Profesor de Carrera Asociado C<br>Departamento de Matemáticas<br>Facultad de Ciencias<br>Universidad Nacional Autónoma de México</font></div></div></div></div></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)