pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Amn Ojee Uw <amnojeeuw@gmail.com>
To: Adrian Klaver <adrian.klaver@aklaver.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: error: connection to server on socket...
Date: Tue, 1 Aug 2023 18:40:03 -0400
Message-ID: <e03e16fe-e51f-1772-b2ed-a83d21b4655a@gmail.com> (raw)
In-Reply-To: <11ee7173-cfb6-7f4c-c17b-dcced24e2bc9@aklaver.com>
References: <97d77785-22a0-5d48-9582-4a7beb2dc14f@gmail.com>
	<863bf07c-6993-ce36-f260-6749ab327632@aklaver.com>
	<148c784c-8eac-0bae-43c9-f819d265e288@gmail.com>
	<11ee7173-cfb6-7f4c-c17b-dcced24e2bc9@aklaver.com>

Thank you Adrian. It Worked!!!


On 8/1/23 2:55 p.m., Adrian Klaver wrote:
> On 8/1/23 11:42, Amn Ojee Uw wrote:
>> Ah! Adrean, here is something interesting.
>>
>> /*pg_lsclusters*/ displays the following information
>>
>> /*Ver Cluster Port Status                Owner    Data 
>> directory              Log file*//*
>> *//*12  main    5432 down,binaries_missing postgres 
>> /var/lib/postgresql/12/main 
>> /var/log/postgresql/postgresql-12-main.log*//*
>> *//*15  main    5433 online                postgres 
>> /var/lib/postgresql/15/main /var/log/postgresql/postgresql-15-main.log*/
>>
>> What is version 12 is doing there, I thought that I had completely 
>> removed it and replaced it with version 15!!
>
> You didn't, read:
>
> https://www.postgresql.org/message-id/20230731125247.puiaz7fjkfvljdwy%40alvherre.pgsql 
>
>
> and
>
> https://www.postgresql.org/message-id/33f0fc61-2d0f-60bd-e0ed-4cada3c30301@aklaver.com 
>
>
> The clue is "binaries_missing".
>
> You remove(ed) all the files except the conf files.
>
>
>> Should I remove that log file?
>
> Run:
>
> sudo apt purge postgresql-12
>
> That will take care of removing all the conf files.
>
>
> To connect you need to specify the correct port, 5433 or do:
>
> sudo vi /etc/postgresql/15/main/postgresql.conf
>
> and change
>
> port = 5433
>
> to
>
> port = 5432
>
> Then restart the server.
>
> You then need to spend some time at the links in this message:
>
> https://www.postgresql.org/message-id/c1ad730a-a84a-ae97-2f23-6891cb06ef26%40aklaver.com 
>
>
>>
>> Regarding /pf@pfortin.com/ assertion, I am working with a _/Debian 
>> 12/_ machine and /*ls -l /tmp/.s.PGSQL.5432*/
>> displays the following error message : /*ls: cannot access 
>> '/tmp/.s.PGSQL.5432': No such file or directory*/
>>
>> As for Tomas Pospisek questions :
>> * as which user are you doing that (you can see that via `id`)?
>>
>>     Due to matters of security let us assume that the output is :
>>     /*id*//*
>>     *//*uid=1000(my_account) gid=1000(my_account)
>> groups=1000(my_account),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),100(users),*/
>> /*106(netdev),111(bluetooth),113(lpadmin),116(scanner),122(postgres),1001(tomcat)*/
>>
>> * in which directory are you executing it  (you can see that via `pwd`)?
>>
>>     /*/home/*//*my_account*/
>>
>> * what is the home directory of the postgres user (you can see that 
>> via `grep postgres /etc/passwd`) /*
>> */
>>
>>     /*~$ grep postgres /etc/passwd*//*
>>     *//*postgres:x:113:122:PostgreSQL
>>     administrator,,,:/var/lib/postgresql:/bin/bash*/
>>
>> * what does `ls -ld /var/run/postgresql/; ls -l 
>> /var/run/postgresql/.s.PGSQL.5432` show?
>>
>>     /*ls -ld /var/run/postgresql/*//*
>>     *//*drwxrwsr-x 2 postgres postgres 100 Jul 31 20:45
>>     /var/run/postgresql/*/
>>
>>     /*ls -l /var/run/postgresql/.s.PGSQL.5432*//*
>>     *//*ls: cannot access '/var/run/postgresql/.s.PGSQL.5432': No such
>>     file or directory*/
>>
>>
>> - what does `journalctl -xeu postgresql` say?
>>
>>     /*sudo journalctl -xeu postgresql*//*
>>     *//*[sudo] password for *//*/**//*my_account*/: *//*
>>     *//*░░ Support: https://www.debian.org/support*//*
>>     *//*░░ *//*
>>     *//*░░ A start job for unit postgresql.service has begun 
>> execution.*//*
>>     *//*░░ *//*
>>     *//*░░ The job identifier is 3496.*//*
>>     *//*Jul 31 20:45:13 *//*tree.com systemd[1]: Finished
>>     postgresql.service - PostgreSQL R>*//*
>>     *//*░░ Subject: A start job for unit postgresql.service has finished
>>     successfully*//*
>>     *//*░░ Defined-By: systemd*//*
>>     *//*░░ Support: https://www.debian.org/support*//*
>>     *//*░░ *//*
>>     *//*░░ A start job for unit postgresql.service has finished
>>     successfully.*//*
>>     *//*░░ *//*
>>     *//*░░ The job identifier is 3496.*//*
>>     *//*lines 4-16/16 (END)*/
>>
>> - what does `tail -n 20 
>> /var/log/postgresql/postgresql-*-qgisclouddb.log` show?
>>
>>     /*sudo tail -n 20 
>> /var/log/postgresql/postgresql-*-qgisclouddb.log*//*
>>     *//*tail: cannot open
>>     '/var/log/postgresql/postgresql-*-qgisclouddb.log' for reading: No
>>     such file or directory*/
>>
>>
>> I hope I was able to answer all the interesting questions posted as 
>> reply to my original post.
>>
>> /Thanks folks, I really appreciate the time you have dedicated to my 
>> question./
>>
>>
>> On 8/1/23 10:35 a.m., Adrian Klaver wrote:
>>> On 8/1/23 03:22, Amn Ojee Uw wrote:
>>>> Using the following command on my Debian 12 machine:
>>>>
>>>> /*sudo apt-get install postgresql postgresql-15 
>>>> postgresql-client-common postgresql-common postgresql-contrib 
>>>> postgresql-doc phppgadmin
>>>> */
>>>>
>>>>
>>>> and following the instruction on this 
>>>> <https://wiki.debian.org/PostgreSql#User_access; web page I have 
>>>> installed PostgreSQL-15.
>>>> The installation went smooth, until the following command was issued :
>>>>
>>>> /*sudo -u postgres psql*/
>>>>
>>>> ... I get an error message that reads:
>>>>
>>>> /*could not change directory to "/home/my_account": Permission 
>>>> denied*//*
>>>> *//*psql: error: connection to server on socket 
>>>> "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or 
>>>> directory*//*
>>>> *//*    Is the server running locally and accepting connections on 
>>>> that socket?*/
>>>>
>>>> What can I do to resolve this issue?
>>>
>>> Run
>>>
>>> pg_lsclusters
>>>
>>> and see what port the server is running on.
>>>
>>>>
>>>> Thanks in advance.
>>>>
>>>
>





view thread (10+ messages)

Message-ID: <e03e16fe-e51f-1772-b2ed-a83d21b4655a@gmail.com>
Permalink:  ../e03e16fe-e51f-1772-b2ed-a83d21b4655a@gmail.com/
Also on:    postgresql.org/message-id/e03e16fe-e51f-1772-b2ed-a83d21b4655a@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: amnojeeuw@gmail.com, adrian.klaver@aklaver.com
  Subject: Re: error: connection to server on socket...
  In-Reply-To: <e03e16fe-e51f-1772-b2ed-a83d21b4655a@gmail.com>
  References: <97d77785-22a0-5d48-9582-4a7beb2dc14f@gmail.com> <863bf07c-6993-ce36-f260-6749ab327632@aklaver.com> <148c784c-8eac-0bae-43c9-f819d265e288@gmail.com> <11ee7173-cfb6-7f4c-c17b-dcced24e2bc9@aklaver.com> <e03e16fe-e51f-1772-b2ed-a83d21b4655a@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox