Hi Gordon,
Thanks that fixed the issue, indeed I configured it to listen on a
specific IP.
I didn't know the exact difference between network and network-online
targets.
Best regards,
Alexis.
Le vendredi 09 juin 2017 à 17:31 -0700, Gordon Messmer a écrit :
> On 06/09/2017 12:09 AM, Jeandet Ale
On 06/09/2017 12:09 AM, Jeandet Alexis wrote:
On startup postgreslq always fail to start complaining about port 5432.
My first guess would be that you've configured postgresql to listen on a
specific IP address, and when you do that, the service needs to depend
on "network-online.target" ins
On 06/09/2017 12:09 AM, Jeandet Alexis wrote:
I have a server running F25 with postgresql and firewald configured.
On startup postgreslq always fail to start complaining about port 5432.
I did allow this port on the firewall, if I start manually postgresql
after it works.
Can you paste the ex
Hello,
I have a server running F25 with postgresql and firewald configured.
On startup postgreslq always fail to start complaining about port 5432.
I did allow this port on the firewall, if I start manually postgresql
after it works.
So I did plot the startup sequence (systemd-analyse plot), I saw
