Re: Sebastian Elisa Pfeifer 2018-09-07 <ab23ab6a-f54a-4063-be3d-dbc93f5dedd2@ixolit.com>
> |2018-09-06 14:02:32 UTC LOG: could not bind IPv4 socket: Cannot assign
> requested address 2018-09-06 14:02:32 UTC HINT: Is another postmaster
> already running on port 5432? If not, wait a few seconds and retry.
> 2018-09-06 14:02:32 UTC WARNING: could not create listen socket for
> "123.123.123.123"|
>
> Possible fix: Adding the parameter After=network-online.target to it's
> SystemD Unit file.
>
> Our setup includes the setting:
> listen_addresses = 'localhost,123.123.123.123' (not the real IP)
Hi,
thanks for the report.
I'll have to investigate if that's the correct fix in general. Afaict
network-online.target does less than what the name says, i.e. some
interfaces might still be configuring even at that point. Usual
symptoms are IPv6 devices that are still in address discovery.
I'll let you know what the outcome is.
Christoph