right. It was clear, but not correct I am afraid. Apologies.
I meant it the other way around. Checking whether postgres1 can be connected to
FROM another machine.
Still the hint to the wait module was real value for me, thanks for that.
> On 06/05/2023 1:07 PM CEST Vladimir Botka wrote:
>
On Mon, 5 Jun 2023 11:53:44 +0200 (CEST)
dulhaver via Ansible Project wrote:
> probably I did not make myself clear enough
No. Your statement can't be clearer: "to check whether postgres1 has
a connection via port 5432 to a specific IP address"
probably I did not make myself clear enough
> - hosts: postgres1
> tasks:
> - wait_for:
> host:
> port: 5432
I guess this would check whether 'postgres1' can connect to :5432.
What I wanted to check (without waiting for a connection to be ready actually,
just
On Sun, 4 Jun 2023 12:06:39 +0200 (CEST)
dulhaver via Ansible Project wrote:
> ... couple of postgres-remotes ...
> ... to check whether postgres1 has a connection via port 5432 to a specific
> IP address ...
> ... what would be the right approach (aka module) for such in an Ansible TASK?
Use
Do you want to check if the server has an established connection to an IP
address?
Or if it is listening on a specific port?
There are perhaps better ways of finding out if a server is running at some
socket
On Sun, 4 Jun 2023 at 12:06, dulhaver via Ansible Project <
hi,
I am running a playbook og a couple of postgres-remotes who play different
roles in a complex server landscape.
Now I want to check to check whether i.e. postgres1 has a connection via port
5432 to a specific IP address. The true/false like result of such a check
should be saved into a
