Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #241761 > unrolled thread

OpenSMTPD won't start as part of systemd

Back to article view | Back to linux.debian.user

Contents

  OpenSMTPD won't start as part of systemd "Paul M. Foster" <paulf@quillandmouse.com> - 2021-10-28 23:10 +0200
    Re: OpenSMTPD won't start as part of systemd Greg Wooledge <greg@wooledge.org> - 2021-10-28 23:30 +0200
      Re: OpenSMTPD won't start as part of systemd "Paul M. Foster" <paulf@quillandmouse.com> - 2021-10-29 04:00 +0200
        Re: OpenSMTPD won't start as part of systemd Greg Wooledge <greg@wooledge.org> - 2021-10-29 04:20 +0200
          Re: OpenSMTPD won't start as part of systemd "Paul M. Foster" <paulf@quillandmouse.com> - 2021-10-29 07:00 +0200
            Re: OpenSMTPD won't start as part of systemd john doe <johndoe65534@mail.com> - 2021-10-29 08:10 +0200
            Re: OpenSMTPD won't start as part of systemd Greg Wooledge <greg@wooledge.org> - 2021-10-29 14:10 +0200
              Re: OpenSMTPD won't start as part of systemd "Paul M. Foster" <paulf@quillandmouse.com> - 2021-10-29 15:20 +0200
                Re: OpenSMTPD won't start as part of systemd john doe <johndoe65534@mail.com> - 2021-10-29 16:40 +0200
        Re: OpenSMTPD won't start as part of systemd David Wright <deblis@lionunicorn.co.uk> - 2021-10-29 04:40 +0200
          Re: OpenSMTPD won't start as part of systemd "Paul M. Foster" <paulf@quillandmouse.com> - 2021-10-29 07:40 +0200
            Re: OpenSMTPD won't start as part of systemd john doe <johndoe65534@mail.com> - 2021-10-29 08:20 +0200
            Re: OpenSMTPD won't start as part of systemd Jonathan Dowland <jon+debian-user@dow.land> - 2021-10-29 10:50 +0200

#241761 — OpenSMTPD won't start as part of systemd

Folks:

This is just an annoyance, but it really shouldn't happen. As my system 
is rebooting, and all the startup chatter echos to the screen, I notice 
that OpenSMTPd fails to start. Once I'm logged in, I can start it 
manually with no problem. When I look at the failure mode, it appears 
that it thinks the "eno1" interface isn't functioning, so it can't 
monitor that interface. The config file for OpenSMTPd specifies that it 
should listen on localhost and eno1. I looks at the systemd config file 
for this package, and it specifies that this unit should executed after 
"network.target" ("After=network.target"). I'm not that familiar with 
systemd.

Any clues on how to fix this? Is it a systemd problem, or something else?

Paul

[toc] | [next] | [standalone]

#241762

On Thu, Oct 28, 2021 at 04:42:52PM -0400, Paul M. Foster wrote:
> Folks:
> 
> This is just an annoyance, but it really shouldn't happen. As my system is
> rebooting, and all the startup chatter echos to the screen, I notice that
> OpenSMTPd fails to start. Once I'm logged in, I can start it manually with
> no problem. When I look at the failure mode, it appears that it thinks the
> "eno1" interface isn't functioning, so it can't monitor that interface.

Are you bringing up eno1 with /etc/network/interfaces?  If so, make
sure it's marked as "auto", not as "allow-hotplug".

[toc] | [prev] | [next] | [standalone]

#241763

On 10/28/21 5:11 PM, Greg Wooledge wrote:
> On Thu, Oct 28, 2021 at 04:42:52PM -0400, Paul M. Foster wrote:
>> Folks:
>>
>> This is just an annoyance, but it really shouldn't happen. As my system is
>> rebooting, and all the startup chatter echos to the screen, I notice that
>> OpenSMTPd fails to start. Once I'm logged in, I can start it manually with
>> no problem. When I look at the failure mode, it appears that it thinks the
>> "eno1" interface isn't functioning, so it can't monitor that interface.
> Are you bringing up eno1 with /etc/network/interfaces?  If so, make
> sure it's marked as "auto", not as "allow-hotplug".

Well, that's interesting. Here is my /etc/network/interfaces:

===

source /etc/network/interfaces.d/*


# The loopback network interface

auto lo

iface lo inet loopback

===

There's nothing in /etc/network/interfaces.d/ . This is a stock Debian 
11 install, so whatever's in this file hasn't been messed with. No 
mention of eno1. However, it DOES come up. Any clues?

Paul

[toc] | [prev] | [next] | [standalone]

#241764

On Thu, Oct 28, 2021 at 09:34:26PM -0400, Paul M. Foster wrote:
> Well, that's interesting. Here is my /etc/network/interfaces:
> 
> ===
> 
> source /etc/network/interfaces.d/*
> 
> 
> # The loopback network interface
> 
> auto lo
> 
> iface lo inet loopback
> 
> ===
> 
> There's nothing in /etc/network/interfaces.d/ . This is a stock Debian 11
> install, so whatever's in this file hasn't been messed with. No mention of
> eno1. However, it DOES come up. Any clues?

There's no such thing as a "stock install".  There are many possible
installs, depending on which choices you make during the installation.

If your interface isn't defined in /e/n/i then the most likely place
it's being brought up is in Network-Manager.  If it's not N-M then
perhaps someone has configured your system to use systemd-networkd,
but that's not enabled by default in Debian, so it's far less common.

[toc] | [prev] | [next] | [standalone]

#241766

On 10/28/21 9:59 PM, Greg Wooledge wrote:
> On Thu, Oct 28, 2021 at 09:34:26PM -0400, Paul M. Foster wrote:
>> Well, that's interesting. Here is my /etc/network/interfaces:
>>
>> ===
>>
>> source /etc/network/interfaces.d/*
>>
>>
>> # The loopback network interface
>>
>> auto lo
>>
>> iface lo inet loopback
>>
>> ===
>>
>> There's nothing in /etc/network/interfaces.d/ . This is a stock Debian 11
>> install, so whatever's in this file hasn't been messed with. No mention of
>> eno1. However, it DOES come up. Any clues?
> There's no such thing as a "stock install".  There are many possible
> installs, depending on which choices you make during the installation.
>
> If your interface isn't defined in /e/n/i then the most likely place
> it's being brought up is in Network-Manager.  If it's not N-M then
> perhaps someone has configured your system to use systemd-networkd,
> but that's not enabled by default in Debian, so it's far less common.
>

How about "/etc/NetworkManager/system-connections/Wired connection 1" 
(who comes up with these Windows filenames?):

===

[connection]
id=Wired connection 1
uuid=7bb23b3a-c750-4c65-ae82-164f7359ea7d
type=802-3-ethernet

[802-3-ethernet]

[ipv4]
method=auto

[ipv6]
method=auto
ip6-privacy=2

===

"Stock install" in this case means I just let the installer set up the 
networking, etc. Since eno1 is the wired connection, I assume this is 
where it gets set up. However, this doesn't really answer the question 
of why eno1 apparently not ready when OpenSMTPd wants to start.

Paul

[toc] | [prev] | [next] | [standalone]

#241768

On 10/29/2021 6:39 AM, Paul M. Foster wrote:
>
> On 10/28/21 9:59 PM, Greg Wooledge wrote:
>> On Thu, Oct 28, 2021 at 09:34:26PM -0400, Paul M. Foster wrote:
>>> Well, that's interesting. Here is my /etc/network/interfaces:
>>>
>>> ===
>>>
>>> source /etc/network/interfaces.d/*
>>>
>>>
>>> # The loopback network interface
>>>
>>> auto lo
>>>
>>> iface lo inet loopback
>>>
>>> ===
>>>
>>> There's nothing in /etc/network/interfaces.d/ . This is a stock
>>> Debian 11
>>> install, so whatever's in this file hasn't been messed with. No
>>> mention of
>>> eno1. However, it DOES come up. Any clues?
>> There's no such thing as a "stock install".  There are many possible
>> installs, depending on which choices you make during the installation.
>>
>> If your interface isn't defined in /e/n/i then the most likely place
>> it's being brought up is in Network-Manager.  If it's not N-M then
>> perhaps someone has configured your system to use systemd-networkd,
>> but that's not enabled by default in Debian, so it's far less common.
>>
>
> How about "/etc/NetworkManager/system-connections/Wired connection 1"
> (who comes up with these Windows filenames?):
>
> ===
>
> [connection]
> id=Wired connection 1
> uuid=7bb23b3a-c750-4c65-ae82-164f7359ea7d
> type=802-3-ethernet
>
> [802-3-ethernet]
>
> [ipv4]
> method=auto
>
> [ipv6]
> method=auto
> ip6-privacy=2
>
> ===
>
> "Stock install" in this case means I just let the installer set up the
> networking, etc. Since eno1 is the wired connection, I assume this is
> where it gets set up. However, this doesn't really answer the question
> of why eno1 apparently not ready when OpenSMTPd wants to start.
>

Race condition, it looks like your interface is broaght up after the
smtp service.

--
John Doe

[toc] | [prev] | [next] | [standalone]

#241774

On Fri, Oct 29, 2021 at 12:39:09AM -0400, Paul M. Foster wrote:
> "Stock install" in this case means I just let the installer set up the
> networking, etc.

How that happens depends on which tasks you selected during the
installation.  If you go with "Standard" (as one often does when
installing for a server), network-manager is not installed.  But if
you select any of the desktop environment packages, N-M *is* installed,
and then networking is configured using that instead of /e/n/i.

I'm guessing you installed a desktop environment task during the
original installation on this machine.

[toc] | [prev] | [next] | [standalone]

#241781

On 10/29/21 7:44 AM, Greg Wooledge wrote:
> On Fri, Oct 29, 2021 at 12:39:09AM -0400, Paul M. Foster wrote:
>> "Stock install" in this case means I just let the installer set up the
>> networking, etc.
> How that happens depends on which tasks you selected during the
> installation.  If you go with "Standard" (as one often does when
> installing for a server), network-manager is not installed.  But if
> you select any of the desktop environment packages, N-M *is* installed,
> and then networking is configured using that instead of /e/n/i.
>
> I'm guessing you installed a desktop environment task during the
> original installation on this machine.
>
And you would be correct.

Paul

[toc] | [prev] | [next] | [standalone]

#241786

On 10/29/2021 2:55 PM, Paul M. Foster wrote:
> On 10/29/21 7:44 AM, Greg Wooledge wrote:
>> On Fri, Oct 29, 2021 at 12:39:09AM -0400, Paul M. Foster wrote:
>>> "Stock install" in this case means I just let the installer set up the
>>> networking, etc.
>> How that happens depends on which tasks you selected during the
>> installation.  If you go with "Standard" (as one often does when
>> installing for a server), network-manager is not installed.  But if
>> you select any of the desktop environment packages, N-M *is* installed,
>> and then networking is configured using that instead of /e/n/i.
>>
>> I'm guessing you installed a desktop environment task during the
>> original installation on this machine.
>>
> And you would be correct.
>

Is this service 'NetworkManager-wait-online.service' (1) enabled, that
is if you use NM?

1)  https://wiki.archlinux.org/title/Systemd

--
John Doe

[toc] | [prev] | [next] | [standalone]

#241765

On Thu 28 Oct 2021 at 21:34:26 (-0400), Paul M. Foster wrote:
> On 10/28/21 5:11 PM, Greg Wooledge wrote:
> > On Thu, Oct 28, 2021 at 04:42:52PM -0400, Paul M. Foster wrote:
> > > This is just an annoyance, but it really shouldn't happen. As my system is
> > > rebooting, and all the startup chatter echos to the screen, I notice that
> > > OpenSMTPd fails to start. Once I'm logged in, I can start it manually with
> > > no problem. When I look at the failure mode, it appears that it thinks the
> > > "eno1" interface isn't functioning, so it can't monitor that interface.
> > Are you bringing up eno1 with /etc/network/interfaces?  If so, make
> > sure it's marked as "auto", not as "allow-hotplug".
> 
> Well, that's interesting. Here is my /etc/network/interfaces:
> 
> ===
> source /etc/network/interfaces.d/*
> # The loopback network interface
> auto lo
> iface lo inet loopback
> ===
> 
> There's nothing in /etc/network/interfaces.d/ . This is a stock Debian
> 11 install, so whatever's in this file hasn't been messed with. No
> mention of eno1. However, it DOES come up. Any clues?

Perhaps look at your logs and dmesg; and post how your networking is
intended to come up.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#241767

On 10/28/21 10:17 PM, David Wright wrote:
> On Thu 28 Oct 2021 at 21:34:26 (-0400), Paul M. Foster wrote:
>> On 10/28/21 5:11 PM, Greg Wooledge wrote:
>>> On Thu, Oct 28, 2021 at 04:42:52PM -0400, Paul M. Foster wrote:
>>>> This is just an annoyance, but it really shouldn't happen. As my system is
>>>> rebooting, and all the startup chatter echos to the screen, I notice that
>>>> OpenSMTPd fails to start. Once I'm logged in, I can start it manually with
>>>> no problem. When I look at the failure mode, it appears that it thinks the
>>>> "eno1" interface isn't functioning, so it can't monitor that interface.
>>> Are you bringing up eno1 with /etc/network/interfaces?  If so, make
>>> sure it's marked as "auto", not as "allow-hotplug".
>> Well, that's interesting. Here is my /etc/network/interfaces:
>>
>> ===
>> source /etc/network/interfaces.d/*
>> # The loopback network interface
>> auto lo
>> iface lo inet loopback
>> ===
>>
>> There's nothing in /etc/network/interfaces.d/ . This is a stock Debian
>> 11 install, so whatever's in this file hasn't been messed with. No
>> mention of eno1. However, it DOES come up. Any clues?
> Perhaps look at your logs and dmesg; and post how your networking is
> intended to come up.
>
> Cheers,
> David.
>

A lot to examine...

One thing stands out. There is an error of sorts in /etc/daemon.log:

Oct 26 17:44:05 dudley systemd-udevd[271]: 
/usr/lib/udev/rules.d/80-ifupdown.rules: 2 Unknown group 'netdev', ignoring

I "accidentally" deleted the "netdev" group a few days ago. I wonder if 
that's the reason.

Paul

[toc] | [prev] | [next] | [standalone]

#241769

On 10/29/2021 7:16 AM, Paul M. Foster wrote:
>
> On 10/28/21 10:17 PM, David Wright wrote:
>> On Thu 28 Oct 2021 at 21:34:26 (-0400), Paul M. Foster wrote:
>>> On 10/28/21 5:11 PM, Greg Wooledge wrote:
>>>> On Thu, Oct 28, 2021 at 04:42:52PM -0400, Paul M. Foster wrote:
>>>>> This is just an annoyance, but it really shouldn't happen. As my
>>>>> system is
>>>>> rebooting, and all the startup chatter echos to the screen, I
>>>>> notice that
>>>>> OpenSMTPd fails to start. Once I'm logged in, I can start it
>>>>> manually with
>>>>> no problem. When I look at the failure mode, it appears that it
>>>>> thinks the
>>>>> "eno1" interface isn't functioning, so it can't monitor that
>>>>> interface.
>>>> Are you bringing up eno1 with /etc/network/interfaces?  If so, make
>>>> sure it's marked as "auto", not as "allow-hotplug".
>>> Well, that's interesting. Here is my /etc/network/interfaces:
>>>
>>> ===
>>> source /etc/network/interfaces.d/*
>>> # The loopback network interface
>>> auto lo
>>> iface lo inet loopback
>>> ===
>>>
>>> There's nothing in /etc/network/interfaces.d/ . This is a stock Debian
>>> 11 install, so whatever's in this file hasn't been messed with. No
>>> mention of eno1. However, it DOES come up. Any clues?
>> Perhaps look at your logs and dmesg; and post how your networking is
>> intended to come up.
>>
>> Cheers,
>> David.
>>
>
> A lot to examine...
>
> One thing stands out. There is an error of sorts in /etc/daemon.log:
>
> Oct 26 17:44:05 dudley systemd-udevd[271]:
> /usr/lib/udev/rules.d/80-ifupdown.rules: 2 Unknown group 'netdev', ignoring
>
> I "accidentally" deleted the "netdev" group a few days ago. I wonder if
> that's the reason.
>

If it was working before that removal, that's probably it!!! :)

--
John Doe

[toc] | [prev] | [next] | [standalone]

#241771

On Fri, Oct 29, 2021 at 01:16:12AM -0400, Paul M. Foster wrote:
>A lot to examine...

If you've got journald installed and configured (likely) you can narrow
it down a little with journalctl. You want messages from the beginning
of the last boot up until the point that opensmtpd complained.

    journalctl -xb --until="YYYY-MM-DD HH:MM:SS"

>One thing stands out. There is an error of sorts in /etc/daemon.log:
>
>Oct 26 17:44:05 dudley systemd-udevd[271]: 
>/usr/lib/udev/rules.d/80-ifupdown.rules: 2 Unknown group 'netdev', 
>ignoring
>
>I "accidentally" deleted the "netdev" group a few days ago. I wonder 
>if that's the reason.

I suspect this is not related. From reading up-ifupdown.rules, it would
seem that the rule only triggers for interfaces marked allow-hotplug,
which implies defined in /etc/network/interfaces and we've established
that your interface is not defined in there.

However it's probably worth restoring the netdev group, just to be sure
(and to silence that warning). It does not have a stable GID but is
allocated from the system range, so do

    # addgroup --system netdev

In terms of your actual problem, if your Ethernet connection is
ever-present and relatively stable, you could consider defining it in
/etc/network/interfaces instead of relying on NetworkManager. I suspect
that would side-step the issue. You would do so by adding something like
this to /etc/network/interfaces

    auto en0
    iface en0 inet dhcp

(or static, if you prefer, see interfaces(5))


-- 
Please do not CC me for listmail.

👱🏻	Jonathan Dowland
✎	 jmtd@debian.org
🔗	https://jmtd.net

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web