On 2021-07-29 09:57:39 -0400, Wietse Venema wrote:
> Vincent Lefevre:
> > No, this was the first thing I tried in order to solve the issue[*],
> > but unfortunately this didn't have any effect: it doesn't seem to work
> > with on-demand automount.
>
> If it is always required (for Postfix) what
On 28.07.21 12:54, Jim Garrison wrote:
This means that Postfix now starts up before the network is completely
up, and systemd's DNS resolution hack (systemd-resolved.service),
finding no interfaces up yet, resolves 'localhost' to 127.0.0.2.
(man systemd-resolved.service)
On 7/29/2021 12:34
On 7/29/2021 12:34 AM, Matus UHLAR - fantomas wrote:
On 28.07.21 12:54, Jim Garrison wrote:
This means that Postfix now starts up before the network is completely
up, and systemd's DNS resolution hack (systemd-resolved.service),
finding no interfaces up yet, resolves 'localhost' to 127.0.0.2.
Vincent Lefevre:
> On 2021-07-29 10:54:11 +0200, Daniele Nicolodi wrote:
> > On 29/07/2021 00:17, Vincent Lefevre wrote:
> > > On 2021-07-28 16:49:20 -0400, Wietse Venema wrote:
> > >> Thanks. I agree, Postfix should start up after the network is fully
> > >> initialized. That includes all the
On 2021-07-29 10:54:11 +0200, Daniele Nicolodi wrote:
> On 29/07/2021 00:17, Vincent Lefevre wrote:
> > On 2021-07-28 16:49:20 -0400, Wietse Venema wrote:
> >> Thanks. I agree, Postfix should start up after the network is fully
> >> initialized. That includes all the network interfaces, and all
On 29/07/2021 00:17, Vincent Lefevre wrote:
> On 2021-07-28 16:49:20 -0400, Wietse Venema wrote:
>> Thanks. I agree, Postfix should start up after the network is fully
>> initialized. That includes all the network interfaces, and all the
>> network infrastructure services.
>
> And the disks are
On 28.07.21 12:54, Jim Garrison wrote:
This means that Postfix now starts up before the network is completely
up, and systemd's DNS resolution hack (systemd-resolved.service),
finding no interfaces up yet, resolves 'localhost' to 127.0.0.2.
(man systemd-resolved.service)
sorry, but this
On 2021-07-28 16:49:20 -0400, Wietse Venema wrote:
> Thanks. I agree, Postfix should start up after the network is fully
> initialized. That includes all the network interfaces, and all the
> network infrastructure services.
And the disks are mounted. On my Debian server, I had to add a
Jim Garrison:
> The simple fix is to create an override file with
>
> systemctl edit postfix.service"
>
> and restore the "After=" dependency on network-online.target
Wietse:
> Thanks. I agree, Postfix should start up after the network is fully
> initialized. That includes all the network
On 7/28/2021 1:49 PM, Wietse Venema wrote:
Jim Garrison:
For anyone encountering this error, I've traced it to a regression of
a very old bug relating to systemd service ordering dependencies.
In my case, OS is CentOS Linux release 8.4.2105
postfix-3.5.8-1.el8.x86_64
Since a recent update
Jim Garrison:
> For anyone encountering this error, I've traced it to a regression of
> a very old bug relating to systemd service ordering dependencies.
>
> In my case, OS is CentOS Linux release 8.4.2105
> postfix-3.5.8-1.el8.x86_64
>
> Since a recent update I've found that, after every
For anyone encountering this error, I've traced it to a regression of
a very old bug relating to systemd service ordering dependencies.
In my case, OS is CentOS Linux release 8.4.2105
postfix-3.5.8-1.el8.x86_64
Since a recent update I've found that, after every reboot, Postfix fails
to start,
12 matches
Mail list logo
