Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJlPu-006bim-20 for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 02:51:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sJlPr-007dmu-T6 for pgsql-general@arkaria.postgresql.org; Wed, 19 Jun 2024 02:51:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJlPr-007dmm-Fl for pgsql-general@lists.postgresql.org; Wed, 19 Jun 2024 02:51:20 +0000 Received: from mail-yb1-xb29.google.com ([2607:f8b0:4864:20::b29]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sJlPl-0020iP-EB for pgsql-general@lists.postgresql.org; Wed, 19 Jun 2024 02:51:19 +0000 Received: by mail-yb1-xb29.google.com with SMTP id 3f1490d57ef6-df4d5d0b8d0so6271438276.2 for ; Tue, 18 Jun 2024 19:51:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718765472; x=1719370272; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=0vj0q+NZ7EoMuMak13+FvQMAaqa07+vrXFDzXK/q9Rc=; b=R/xCZ61M7twcc7gdTmKyW4WNoR5hd0Sn5xTjG0XOhqeRN4+qPWwxyOq9O9q8iLuB3a JhtJaqGKk4oz2zHQEATfhDeK5EGbNVkaskk1A/XfvlYR0DVHKDcg9ajTl4aj7GumFivy lB7OcWKVTEsn7cwY+n+BgjQB5LW6vSlmT7FN/ZpG5yxZ9urXOYKXm8WiKRrOSkisAPiv 24shTfS0DfT+vYefD3j8P4LFmoj3rq0kWWcWitLHtwpBQoOEec4s414krVUsmlmNji3T 4b7rAupBHT4jrdfvmuCiXxXOt4pQch2nK5g15nFbFho2wuU2o/ziin7+4kYmnjzcBVJB CMFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718765472; x=1719370272; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=0vj0q+NZ7EoMuMak13+FvQMAaqa07+vrXFDzXK/q9Rc=; b=lbM+Oo/ivSGBy9I5okXv7UoAYYpgrS+zZSyvFJe4A9iIl/CvTNG+FgykeRtTqHDShA mU6RPQnKpffVsFFS4h/0GxuRdkzQAHHfEMd9Q+6AqbiUapaSwLo3lIVqSogy05/2/zkS 134TRXZ77Gs0+eVioRCuDaajaFA1N85gWTQhFia77vKEFfgp3htVIunelPwQ54GJaJ6B lWypco3W1Pz+pgXcjO6KWpmZhzD2+Cyb+rGKkSkFdXqWsLTOivKfhIjMT8qMYrWrsMDo O8fYicGmgukyvcmgkWWZgg0CWlAhtpnd4v/1KUrpeqoqk1ZammtxMRdDRJ57IhZ3TtO7 nzQg== X-Forwarded-Encrypted: i=1; AJvYcCV4A8g0Y/LZXPsiQbyrcsQhH/wP6eNOh60pympj83zjLuewM/159X4Dr7DbgqKXBDzrrFD8mMECgXfAwY1drlRADxa6Nf2Esy6cgQoT+qFw9z5s X-Gm-Message-State: AOJu0YxudfvGLiRrXZ6sydAIUl4clcbJV7a8e16Yt45p+TJOZCESHZJV HS1WN38RCqd7ryYeUTgoJUtSu6HqZ57BrmbzjLn9xiCnMx0KQD6FsjJ9NGhYxRD9t3LxZ8m/A/u 6+bWwHffknwst7tOtNMSMMLGhKrc= X-Google-Smtp-Source: AGHT+IHScCFqTRCmXP+n4L7rVWJYtpWC/wWPNSd8MCsGSY806vzLsmYF6Wcj3nCIMP2PjQyAzoTycFU1xM4Rd7JJ8WI= X-Received: by 2002:a25:a28b:0:b0:e02:3ade:a10a with SMTP id 3f1490d57ef6-e02be22d569mr1737010276.50.1718765472398; Tue, 18 Jun 2024 19:51:12 -0700 (PDT) MIME-Version: 1.0 From: Mukesh Tanuku Date: Wed, 19 Jun 2024 08:20:59 +0530 Message-ID: Subject: Pgpool delegate IP is not reachable from the remote host To: pgpool-general@pgpool.net, pgsql-general@lists.postgresql.org, "vijay.postgres@gmail.com" , bharat.hegde.k@maersk.com Content-Type: multipart/alternative; boundary="0000000000006f49eb061b354583" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006f49eb061b354583 Content-Type: text/plain; charset="UTF-8" Hello everyone. We have a pgpool & postgres setup made as per the given example We haven't configured the *if_up_cmd, if_down_cmd & **arping_cmd* in pgpool.conf (we commented it out on purpose). We enabled the *delegate_ip* and assigned a unused IP. While we bringing up the pgpool the log shows VIP is successfully UP via if_up_cmd, how is this happening? any default way is considering the if_up_cmd to bring the VIP? *2024-06-18 08:27:02.735: watchdog_utility pid 102493: LOG: successfully acquired the delegate IP:"10.127.1.20"2024-06-18 08:27:02.735: watchdog_utility pid 102493: DETAIL: 'if_up_cmd' returned with success2024-06-18 08:27:02.735: watchdog pid 102378: LOG: watchdog escalation process with pid: 102493 exit with SUCCESS.* NOTE: We run into some situation so that we disabled the if_* commands in the configuration and started pgpool, but VIP is getting acquired by the leader pgpool node even the if_* commands are not used in pgpool.conf file. Can anyone explain how the VIP works in pgpool watchdog Thank you Regards Mukesh Tanuku --0000000000006f49eb061b354583 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello everyone.

We have a pgpool & = postgres setup made as per the given example=C2=A0

We haven't configured the=C2=A0if_up_cmd,=C2=A0if_down_cmd &a= mp;=C2=A0arping_cmd = in=C2=A0pgpool.conf (we comment= ed it out on purpose). We enabled the de= legate_ip=C2=A0and assigned a unused IP.

While we bringing up the pgpool the log shows VIP is successfully= UP via=C2=A0if_up_cmd, how is this happening? any default way is= considering the if_up_cmd to bring the VIP?

2024-06-18 08:27= :02.735: watchdog_utility pid 102493: LOG: =C2=A0successfully acquired the = delegate IP:"10.127.1.20"
2024-06-18 08:27:02.735: watchdog_ut= ility pid 102493: DETAIL: =C2=A0'if_up_cmd' returned with success2024-06-18 08:27:02.735: watchdog pid 102378: LOG: =C2=A0watchdog escalat= ion process with pid: 102493 exit with SUCCESS.

NOTE: We run into some situation so that we disabled the if_* = commands in the configuration and started pgpool, but VIP is getting acquir= ed=C2=A0by the leader pgpool node even the if_* commands are not used in pg= pool.conf file.

Can anyone explain how th= e VIP works in pgpool watchdog

Thank you<= /font>
Regards
Mukesh Tanuku
--0000000000006f49eb061b354583--