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 1tLkQv-00Gjaj-Gl for pgsql-admin@arkaria.postgresql.org; Thu, 12 Dec 2024 14:44:53 +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 1tLkQs-00CVja-V9 for pgsql-admin@arkaria.postgresql.org; Thu, 12 Dec 2024 14:44:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tLkQs-00CVjS-Ij for pgsql-admin@lists.postgresql.org; Thu, 12 Dec 2024 14:44:51 +0000 Received: from mail-wm1-x335.google.com ([2a00:1450:4864:20::335]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tLkQq-002Tl6-Ab for pgsql-admin@lists.postgresql.org; Thu, 12 Dec 2024 14:44:50 +0000 Received: by mail-wm1-x335.google.com with SMTP id 5b1f17b1804b1-4361f796586so8424845e9.3 for ; Thu, 12 Dec 2024 06:44:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734014688; x=1734619488; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=u+OIWNpXMOMNt0iZr+xkpiZxfdTotwevOxiAp1/xE2Q=; b=fndgJF3Md5KjalGd5WAqLr9CSuD5MOrTgXeBjriMv3PZU7NE9SvkhQtq+H/YwZuted rqQFFwL8arV8ESfxFPU4wUUG8h9DoPC8pccRkcp8J/vsbk5D+Ry0CP64zqLKd5Ug8tjQ jRyL5nS14R8iIrnQwL2yXu4+M6ijo+wh+mddoJ8ETFN/0xraOv0RiFaPsUFJ6wplzvyz U4F2TGq6MS9Bv5iZRMvUI1jnqfCI38YWyUidDOsIrnL5VuTYm+ptPBcmv5gYOy6XIXjb MdMrHLcC2z15PmtNAHkxC8/yOKFioT/K1+m1IL5GNZDPzM4l91T5h+52re+J8Kafr4HC M3uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734014688; x=1734619488; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=u+OIWNpXMOMNt0iZr+xkpiZxfdTotwevOxiAp1/xE2Q=; b=MI7OnFG/TuDp4zjWFNUHRrxWJ8a9PYK5SCiFQkJerTKYexlYL0L9t4q8yVnFeRjDNu AWLsAJ1n1zJfzWOFARsakzEXA5Twa/KIdN7dFcYhrNRo+0TruyQs762hCZj3p0+XOHYS IYZfnMnkdN1RFvMpxL+VqH1UXiMUryMF1aEZFbuCC/Lo3iRzqxlBg5rwWk34JTeCK0DH 1/xLVQqDd5GXX//M4Rn+Z3PEt8eGsXoAb1J+tRRvvOs70e1/1O3EZZCekv/ilArrXvIu 84r8ckW1FG6nutUm3HlQj31rfDwjjFkzKpR7oBgfb33p63nhM7xeYWNSBuO/6zFqPRxn FHKg== X-Gm-Message-State: AOJu0Yxo2JUrGiMhRvtJkutVSKyrP2qP/VB03SlhXFPlUbqmVKbywRyx t1EUsSPuypihJ3Luzy9ZWuIl844seVu8v+UtcyA4QhDcuQi62Uiv0FNAYOmuIRpjp6AzM4l74WV Dl2ko8c9UuWT8NmAg9MXNM4FuRPU= X-Gm-Gg: ASbGncup/42ag34pyKMXP2Mjedfk8QMjKANfEKoRESUexJ3tgxnJiv3QL7tY8aRfHTG g9FsfF1Td7rTNT8grnY5/97S9ue2o1yaF2r3yC0VT1AK0+AzPUhyXLfJjk6+vQHaO8VANzEzF X-Google-Smtp-Source: AGHT+IGOszCgp/YK6VsXSWkK8OyROzpciXvEkz+iWbc/cTUgFCrrN1YizOErDk7ojrdsNcZbdSjZeCCynkclN6zrkhw= X-Received: by 2002:a05:600c:c89:b0:436:1baa:de1c with SMTP id 5b1f17b1804b1-4361c3aa4dbmr67471815e9.13.1734014687424; Thu, 12 Dec 2024 06:44:47 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: "Narendran .j" Date: Thu, 12 Dec 2024 20:14:36 +0530 Message-ID: Subject: Re: Psql not working To: Kashif Zeeshan Cc: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000007ab67b062913c1ae" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007ab67b062913c1ae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I have checked the user, user is postgres I have noted that in bin path the size of psql client is 0 psql --version and psql --help not working so i suspecting the psql client Regards, Narendran On Thu, 12 Dec 2024 at 19:40, Kashif Zeeshan wrote: > Hi > > Can you check which user you are using to run psql, > > Do the following > 1. Execute ls -lrt /usr/pgsql../bin/psql to see if the user have access t= o > it > > 2. If you have access then try running the command psql --help to make > sure if you have access to psql. > > 3. Also try to connect with the wrong user / port to see if psql generate= s > error. > > Regards > Kashif Zeeshan > > On Thu, Dec 12, 2024 at 6:31=E2=80=AFPM Narendran .j > wrote: > >> Hello Team, >> >> I'm facing one problem, can't login postgres by psql, even it's not >> throwing any error and can't find anything in log. >> >> Checked server is running fine, able to check status using pg_ctl. Can >> can't login through psql >> >> My login attempt >> >> psql >> /usr/pgsql-14/bin/psql >> psql -U postgres -p 5432 -d postgres >> >> When I'm running above query it's return to next line, nothing comes up >> >> Please on this. >> >> Thanks >> > --0000000000007ab67b062913c1ae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I have checked the user, user is postgres
I have noted= that in bin path the size of psql client is 0
psql --version and= psql --help not working
so i suspecting the psql client

Regards,
Narendran

On= Thu, 12 Dec 2024 at 19:40, Kashif Zeeshan <kashi.zeeshan@gmail.com> wrote:
Hi

Can you check which user you are using to run psql,

<= div>Do the following
1. Execute ls -lrt /usr/pgsql../bin/psql to = see if the user have access to it

2. If you have a= ccess then try running the command psql --help to make sure if you have acc= ess to psql.

3. Also try to connect=C2=A0with the = wrong user / port=C2=A0to see if psql generates error.

=
Regards
Kashif Zeeshan

On Thu, Dec 12, 2024 at 6:31=E2= =80=AFPM Narendran .j <jnarendran3@gmail.com> wrote:
Hello Team,

I'm facing one problem, can't logi= n postgres by psql, even it's not throwing any error and can't find= anything in log.

Checke= d server is running fine, able to check status using pg_ctl. Can can't = login through psql

My lo= gin attempt=C2=A0

psql
/usr/pgsql-14/bin/psql
psql -U= postgres -p 5432 -d postgres=C2=A0

When I'm running above query it's return to next line, = nothing comes up

Please = on this.

Thanks
--0000000000007ab67b062913c1ae--