postfix starting before network
David Benfell
benfell at parts-unknown.org
Wed Jul 2 01:39:07 UTC 2014
Rick Stevens writes:
> On 07/01/2014 01:13 PM, David Benfell issued this missive:
>> Hi all,
>>
>> I have no idea why this might be happening. I've looked at the systemd
>> control file for postfix and compared it to dovecot's. Both want the
>> network.target before starting.
>
> "want" is a weakened version of "requires". It doesn't guarantee start
> sequence and if the target fails to start, it doesn't stop THIS service
> from starting ("requires" WOULD prevent this service from starting if
> the target of the "requires" failed).
So this is a bug, then. Neither 'Wants' nor "Requires' was present. It only
had After.
>
>> The difference is that dovecot starts correctly. Postfix does not. The
>> problem has only appeared since Saturday, when I probably did a yum
>> update.
>>
>> Postfix issues an error from one of the pre-commands having to do with
>> the aliases database saying its network interface (and it duly lists
>> the IPv4 address) doesn't exist. Starting postfix manually later
>> works.
>
> Have you checked the postfix.service file and verified it has
> "After=network.target" in it? That should make sure the network starts
> before postfix.
Actually, this is backwards. It didn't have the 'Wants', only the 'After'.
But following your suggestion above, I am adding a 'Requires' instead of
the 'Wants'.
Thanks!
--
David Benfell
See https://parts-unknown.org/node/2 if you do not understand the
attachment.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 811 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20140701/c999d510/attachment.sig>
More information about the users
mailing list