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 1tOa6W-007K81-4d for pgsql-general@arkaria.postgresql.org; Fri, 20 Dec 2024 10:19:32 +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 1tOa6V-008tfV-Eh for pgsql-general@arkaria.postgresql.org; Fri, 20 Dec 2024 10:19:31 +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 1tOa6V-008tfM-2u for pgsql-general@lists.postgresql.org; Fri, 20 Dec 2024 10:19:30 +0000 Received: from mail-yw1-x1135.google.com ([2607:f8b0:4864:20::1135]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tOa6S-000X85-Bi for pgsql-general@lists.postgresql.org; Fri, 20 Dec 2024 10:19:29 +0000 Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-6eeca49d8baso16219487b3.0 for ; Fri, 20 Dec 2024 02:19:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734689967; x=1735294767; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=yGB1Qrf4l6jDoYtsacs1hOpn3j5JPYliTZRLmXlC1CA=; b=T74vpUA6yjCpclTh99M6hxY4BmZtVFXFn6mpFNa/McScuM9prZpqZUnMVaSZcZqgDF XdluDhf6HFB5B5zAfAQKMrODP05qiU7NdlYP1DIhJx/mtZEstONc/pfHrqSMMn3zBqMH JyMX9FHw/FAQfAu4CfBnnJaNQ8IE++SdwHClp+zxnHvugFem7cAOD1YjmI/dvdLVPl6M 5FLhdwE4k6R2Hcjf30P7eYWiJCLEcIDOWaqCo3Zov12umFSSRsAvKl4MWMQHFLOjvExx Z832/ZNherJitt+OChdyzIFkcy10/TI3OTw5Sgra5tGSpr+g6LTSkjaNimREzE9UPKM+ MzAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734689967; x=1735294767; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=yGB1Qrf4l6jDoYtsacs1hOpn3j5JPYliTZRLmXlC1CA=; b=KoNM52OF3r6IQmQUhSEXCg3hF3lTn3tAO6dYQRBGRIsdx2lvxoHJOEWiTUOQufso8c QcC2mH6l7gpBUDg89d8EDhqm32mqrI1rf65efrinT7qJmVoY52graxZk57wnT72twWFW T9sg9dxWFaSe/pk2ddzLHooyanQPhrwlZ4nAEyhWYLEMXs1h23/aUyoChP0/bqr0u6Ii 80VUZN7v3qBwKQz4RrdP3TqtMIgO2iwVnwQvFe0K9jYOnOoF6jum2vl1cSiPLeEeu+0P b9PgdndHU09Vw32xqyoosn0bzUGFwvNF8G6YRfWoun2szHDgYR0p1geCsalUDDVqVsRt I59g== X-Forwarded-Encrypted: i=1; AJvYcCUmjbGmvaL9DdT62clvaOftM2uxhusjdC7MAtC6SbnJ2g1pf7layN5sAEHe7xMiWT+SysEpkjyYzxaR98a0@lists.postgresql.org X-Gm-Message-State: AOJu0YxlW5ADt2DC93ugKuzduNO15aRTdxjCiryHn/FiJjp+/9Uxb5H2 CDD8u5T6OKqMtwRvLD8y2dgEfF1B6urZ/NSs8CxiXynpdDS56uVq8KIiPl+e4a0uI1b52dN/XSF 7iFefJd+f6+psN+aUnQROVvq6H4E= X-Gm-Gg: ASbGncvnLa5l2PE2mUhWf7bgpxC4glgsO4KJYl8nm0fvLzcq17vBhba00NvCiVcTwWD z4iL0p+hHDOa3Fe9lDYnA7cPBZdU5uJtxEN4RzQ== X-Google-Smtp-Source: AGHT+IFFcJ0T1E5CTH87q+71VQEmvhvZlgIm5lM41YqKX4jKyVmluwxnCgyxfuPX/sKgcb6zsfg+rFELBrSYrQtkqh0= X-Received: by 2002:a05:690c:6ac3:b0:6ee:6a2a:a517 with SMTP id 00721157ae682-6f3e2b86036mr52852437b3.18.1734689967681; Fri, 20 Dec 2024 02:19:27 -0800 (PST) MIME-Version: 1.0 From: Mukesh Tanuku Date: Fri, 20 Dec 2024 15:49:16 +0530 Message-ID: Subject: pgpool Connection issue: ERROR: unable to read message kind To: pgpool-general@pgpool.net, vijay.postgres@gmail.com, pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000051b5be0629b0fb77" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000051b5be0629b0fb77 Content-Type: text/plain; charset="UTF-8" Hello Everyone, We have a Postgres setup in Azure (IAAS) with 2 DB nodes in the cluster and pgpool is running on each DB node. We have enabled the watchdog. What we are doing: We are testing the connectivity to DB cluster via HammerDB to apply the load. HammerDB is connecting to Delegate IP via 9999 port. Issue: when we initiate the connection it gives error, but when we re-initiate the connection again then it is successful. What could be the issue Error message we are seeing when we initiate the connection for the first time. Error in Virtual User 1: Error: Connection to database failed connection to server at "10.35.8.4", port 9999 failed: ERROR: unable to read message kind DETAIL: kind does not match between main(53) slot[1] (45) If you want to see any configuration settings that i made, i can share. Please help me in this regard. Thank you Mukesh Tanuku --00000000000051b5be0629b0fb77 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello=C2=A0Everyone,

We have a Post= gres setup in Azure (IAAS) with 2 DB nodes in the cluster and pgpool is run= ning on each DB node. We have enabled the watchdog.=C2=A0

What we are doing: We are testing the connectivity to DB cluster vi= a HammerDB to apply the load.
HammerDB is connecting to Delegate = IP via 9999 port.

Issue: when we initiate the conn= ection it gives error, but when we re-initiate the connection again then it= is successful. What could be the issue

Error mess= age we are seeing when we initiate=C2=A0the connection for the first time.<= /div>

Error in Virtual User 1: E= rror: Connection to database failed
connection to server at "10.35.= 8.4", port 9999 failed: ERROR: =C2=A0unable to read message kind
DE= TAIL: =C2=A0kind does not match between main(53) slot[1] (45)
<= div>
If you want to see any co= nfiguration settings that i made, i can share.

Ple= ase help me in this=C2=A0regard.

Thank you
Mukesh Tanuku
--00000000000051b5be0629b0fb77--