Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g7Isq-0002oa-S4 for pgsql-admin@arkaria.postgresql.org; Tue, 02 Oct 2018 11:30:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g7Iso-0001co-Ao for pgsql-admin@arkaria.postgresql.org; Tue, 02 Oct 2018 11:30:30 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g7Isn-0001ch-Vy for pgsql-admin@lists.postgresql.org; Tue, 02 Oct 2018 11:30:30 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g7IsT-0008BO-Br for pgsql-admin@postgresql.org; Tue, 02 Oct 2018 11:30:28 +0000 Received: from msg.df7cb.de (unknown [IPv6:2003:5b:203b:100:7627:eaff:fe52:8e03]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 42PcQ76JXyz3F0Q; Tue, 2 Oct 2018 13:30:07 +0200 (CEST) Date: Tue, 2 Oct 2018 13:30:07 +0200 From: Christoph Berg To: Mark Steben Cc: pgsql-admin Subject: Re: Fwd: cannot login to psql without specifying host Message-ID: <20181002113007.GI4343@msg.df7cb.de> Mail-Followup-To: Christoph Berg , Mark Steben , pgsql-admin References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Re: Mark Steben 2018-10-02 > *psql -U postgres prime_production -p 5433 * > *psql: could not connect to server: No such file or directory* > * Is the server running locally and accepting* > * connections on Unix domain socket "/tmp/.s.PGSQL.5433"?* > > I have changed the UNIX_SOCKET_DIRECTORIES to something other than /tmp > because we have another instance pointing to that directory. I restarted > postgres. Didn't help. I have attached our 3 config files along with an > ls -la listing of our database cluster directory. Any insights welcome. You can use "psql -h /database/prime_data/PSQL_94/tmp" to use that socket directory. In practise, that will fail for any user than the cluster owner because that is inside your PGDATA, and that is 0700. Christoph