Re: [GENERAL] Unable to start postgresql

On Sat, Mar 11, 2017 at 12:15 AM, Adrian Klaver wrote: > Two resources that help me keep within shouting distance of the latest and > greatest: > > Hubert 'depesz' Lubaczewski > Waiting for PostgreSQL * series: > > https://www.depesz.com/ > In the search box type

Re: [GENERAL] Unable to start postgresql

On 03/10/2017 07:08 AM, John Iliffe wrote: On Friday 10 March 2017 09:25:25 Melvin Davidson wrote: *Probably "PostgreSQL Administration Essentials" would be good to start with.* Thank you. I was unaware of this source. I have a similar book but it is about 8 years old so probably out of

Re: [GENERAL] Unable to start postgresql

On Friday 10 March 2017 09:25:25 Melvin Davidson wrote: > On Thu, Mar 9, 2017 at 10:01 PM, John Iliffe wrote: > > On Thursday 09 March 2017 16:37:28 you wrote: > > > On 03/08/2017 10:12 AM, John Iliffe wrote: > > > > I think you may have hit it but I'm even more confused

Re: [GENERAL] Unable to start postgresql

On Thu, Mar 9, 2017 at 10:01 PM, John Iliffe wrote: > On Thursday 09 March 2017 16:37:28 you wrote: > > On 03/08/2017 10:12 AM, John Iliffe wrote: > > > I think you may have hit it but I'm even more confused now. > > > > > > I looked at the running Postgesql on the current

Re: [GENERAL] Unable to start postgresql

On Thursday 09 March 2017 16:37:28 you wrote: > On 03/08/2017 10:12 AM, John Iliffe wrote: > > I think you may have hit it but I'm even more confused now. > > > > I looked at the running Postgesql on the current server and there is a > > 5th sub-directory called /data. That is on the same level

Re: [GENERAL] Unable to start postgresql

On 03/08/2017 10:12 AM, John Iliffe wrote: I think you may have hit it but I'm even more confused now. I looked at the running Postgesql on the current server and there is a 5th sub-directory called /data. That is on the same level as the /bin, /share, etc. In this new installation it is not

Re: [GENERAL] Unable to start postgresql

On 03/08/2017 10:12 AM, John Iliffe wrote: I think you may have hit it but I'm even more confused now. I looked at the running Postgesql on the current server and there is a 5th sub-directory called /data. That is on the same level as the /bin, /share, etc. In this new installation it is not

Re: [GENERAL] Unable to start postgresql

I think you may have hit it but I'm even more confused now. I looked at the running Postgesql on the current server and there is a 5th sub-directory called /data. That is on the same level as the /bin, /share, etc. In this new installation it is not present and neither is the postgresql.conf

Re: [GENERAL] Unable to start postgresql

On 03/09/2017 08:14 AM, John Iliffe wrote: On Thursday 09 March 2017 09:17:51 Adrian Klaver wrote: On 03/08/2017 09:28 PM, Tom Lane wrote: John Iliffe writes: Comparing my results with Adrian's example, I notice that we both have the Unix domain socket 5432 running

Re: [GENERAL] Unable to start postgresql

On Thursday 09 March 2017 12:49:49 Tom Lane wrote: > John Iliffe writes: > > On Thursday 09 March 2017 12:08:01 Tom Lane wrote: > >> AFAICS, the explanation must be that getaddrinfo() returned two IPv4 > >> addresses, one of which got bound successfully and the other not. >

Re: [GENERAL] Unable to start postgresql

John Iliffe writes: > On Thursday 09 March 2017 12:08:01 Tom Lane wrote: >> AFAICS, the explanation must be that getaddrinfo() returned two IPv4 >> addresses, one of which got bound successfully and the other not. >> The bleat is about the non-working address, but you still

Re: [GENERAL] Unable to start postgresql

On Thursday 09 March 2017 12:08:01 Tom Lane wrote: > John Iliffe writes: > > Here is my matching ss output > > > > -- > > [root@prod04 John]# ss -l -p | grep post > > u_str LISTEN 0 128/tmp/.s.PGSQL.5432 69422 > > *

Re: [GENERAL] Unable to start postgresql

John Iliffe writes: > Here is my matching ss output > -- > [root@prod04 John]# ss -l -p | grep post > u_str LISTEN 0 128/tmp/.s.PGSQL.5432 69422 * > 0 users:(("postgres",pid=2760,fd=5)) > tcp

Re: [GENERAL] Unable to start postgresql

On Thursday 09 March 2017 09:17:51 Adrian Klaver wrote: > On 03/08/2017 09:28 PM, Tom Lane wrote: > > John Iliffe writes: > >> On Wednesday 08 March 2017 23:35:10 Tom Lane wrote: > >>> That isn't proving a lot: as I showed in my example lsof output, > >>> Fedora's lsof will

Re: [GENERAL] Unable to start postgresql

On 03/08/2017 09:28 PM, Tom Lane wrote: > John Iliffe writes: >> On Wednesday 08 March 2017 23:35:10 Tom Lane wrote: >>> That isn't proving a lot: as I showed in my example lsof output, >>> Fedora's lsof will map "5432" to "postgres" in the context of an IP >>> port number.

Re: [GENERAL] Unable to start postgresql

John Iliffe writes: > On Wednesday 08 March 2017 23:35:10 Tom Lane wrote: >> That isn't proving a lot: as I showed in my example lsof output, >> Fedora's lsof will map "5432" to "postgres" in the context of an IP >> port number. (I'm sure there's a way to turn that off, but

Re: [GENERAL] Unable to start postgresql

On Wednesday 08 March 2017 23:35:10 Tom Lane wrote: > John Iliffe writes: > > [root@prod04 John]# lsof -n | grep postmaster > > [root@prod04 John]# lsof -n | grep postgres | grep 5432 > > postgres 2760 postgres5u unix 0x9e5390b5b800 > > 0t0 > > > >

Re: [GENERAL] Unable to start postgresql

John Iliffe writes: > [root@prod04 John]# lsof -n | grep postmaster > [root@prod04 John]# lsof -n | grep postgres | grep 5432 > postgres 2760 postgres5u unix 0x9e5390b5b800 0t0 > 69422 /tmp/.s.PGSQL.5432 type=STREAM That isn't proving

Re: [GENERAL] Unable to start postgresql

On Wednesday 08 March 2017 17:22:21 Adrian Klaver wrote: > On 03/08/2017 01:48 PM, John Iliffe wrote: > > On Wednesday 08 March 2017 15:13:29 Tom Lane wrote: > >> John Iliffe writes: > >>> I tried psql but it won't work, as expected, because socket 5432 is > >>> not

Re: [GENERAL] Unable to start postgresql

On Wednesday 08 March 2017 17:11:16 Adrian Klaver wrote: > On 03/08/2017 02:01 PM, John Iliffe wrote: > > Please use Reply All so others get your posts. > Ccing list > > > On Wednesday 08 March 2017 16:40:03 you wrote: > >> On 03/08/2017 01:28 PM, John Iliffe wrote: > >>>

Re: [GENERAL] Unable to start postgresql

On 03/08/2017 01:48 PM, John Iliffe wrote: On Wednesday 08 March 2017 15:13:29 Tom Lane wrote: John Iliffe writes: I tried psql but it won't work, as expected, because socket 5432 is not available. Actually, that's not all that expected. psql by default would try to

Re: [GENERAL] Unable to start postgresql

On 03/08/2017 02:01 PM, John Iliffe wrote: Please use Reply All so others get your posts. Ccing list On Wednesday 08 March 2017 16:40:03 you wrote: On 03/08/2017 01:28 PM, John Iliffe wrote: --- [root@prod04 John]# su postgres [postgres@prod04 John]$ pg_ctl

Re: [GENERAL] Unable to start postgresql

On Wednesday 08 March 2017 15:13:29 Tom Lane wrote: > John Iliffe writes: > > I tried psql but it won't work, as expected, because socket 5432 is > > not available. > > Actually, that's not all that expected. psql by default would try to > connect via a Unix socket, so it

Re: [GENERAL] Unable to start postgresql

On 03/08/2017 01:28 PM, John Iliffe wrote: On Wednesday 08 March 2017 11:18:59 Adrian Klaver wrote: On 03/08/2017 07:37 AM, John Iliffe wrote: On Wednesday 08 March 2017 00:01:32 Tom Lane wrote: John Iliffe writes: Now, running as user postgres I try and start as

Re: [GENERAL] Unable to start postgresql

On Wednesday 08 March 2017 11:18:59 Adrian Klaver wrote: > On 03/08/2017 07:37 AM, John Iliffe wrote: > > On Wednesday 08 March 2017 00:01:32 Tom Lane wrote: > >> John Iliffe writes: > >>> Now, running as user postgres I try and start as stated in the > >>> manual postgres

Re: [GENERAL] Unable to start postgresql

John Iliffe writes: > I tried psql but it won't work, as expected, because socket 5432 is not > available. Actually, that's not all that expected. psql by default would try to connect via a Unix socket, so it wouldn't matter whether or not the postmaster had been able to

Re: [GENERAL] Unable to start postgresql

On 03/08/2017 10:25 AM, John Iliffe wrote: On Wednesday 08 March 2017 11:37:27 Adrian Klaver wrote: On 03/08/2017 07:37 AM, John Iliffe wrote: On Wednesday 08 March 2017 00:01:32 Tom Lane wrote: John Iliffe writes: Now, running as user postgres I try and start as

Re: [GENERAL] Unable to start postgresql

On 03/08/2017 10:12 AM, John Iliffe wrote: See embedded. Ccing list will not be able to use it. Yes, but if that happens at least I will be able to back out because I can go back and start the old postgresql since it is on a different /usr partition. That's the reason for the install

Re: [GENERAL] Unable to start postgresql

On Wednesday 08 March 2017 11:37:27 Adrian Klaver wrote: > On 03/08/2017 07:37 AM, John Iliffe wrote: > > On Wednesday 08 March 2017 00:01:32 Tom Lane wrote: > >> John Iliffe writes: > >>> Now, running as user postgres I try and start as stated in the > >>> manual postgres

Re: [GENERAL] Unable to start postgresql

Meant to ask before, can you show the command you are using to connect? My memory says OP didn't use --host, which often leads to trying the socket. Do we know that's enabled in pg_hba? -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your

Re: [GENERAL] Unable to start postgresql

On 03/08/2017 07:37 AM, John Iliffe wrote: On Wednesday 08 March 2017 00:01:32 Tom Lane wrote: John Iliffe writes: Now, running as user postgres I try and start as stated in the manual postgres -D /usr/pgsql_tablespaces The result is: [postgres@prod04

Re: [GENERAL] Unable to start postgresql

On 03/08/2017 07:37 AM, John Iliffe wrote: On Wednesday 08 March 2017 00:01:32 Tom Lane wrote: John Iliffe writes: Now, running as user postgres I try and start as stated in the manual postgres -D /usr/pgsql_tablespaces The result is: [postgres@prod04

Re: [GENERAL] Unable to start postgresql

On 03/08/2017 07:44 AM, John Iliffe wrote: See embedded. Just to be clear you installed in: /usr/postgres-9.6.2 yes, and the expected directories /usr/postgres-9.6.2/bin, /include, /lib, and /share are all there. but created the data directory in: /usr/pgsql_tablespaces Yes, I did

Re: [GENERAL] Unable to start postgresql

See embedded. On Wednesday 08 March 2017 00:09:56 Adrian Klaver wrote: > On 03/07/2017 08:17 PM, John Iliffe wrote: > > I was unable to get postgres started so I did a very basic > > compile/install to test it. The configuration line was: > > > > ./configure --prefix=/usr/postgres-9.6.2 > > >

Re: [GENERAL] Unable to start postgresql

On Wednesday 08 March 2017 00:01:32 Tom Lane wrote: > John Iliffe writes: > > Now, running as user postgres I try and start as stated in the manual > > postgres -D /usr/pgsql_tablespaces > > > > The result is: > > [postgres@prod04 postgresql-9.6.2]$ postgres -D

Re: [GENERAL] Unable to start postgresql

On Wed, Mar 8, 2017 at 10:00 AM, Tom Lane wrote: > John Iliffe writes: > > When the programme exited it left another postmaster.pid file so I > deleted > > that one too. > > You haven't shown us the program actually exiting, and basically the only >

Re: [GENERAL] Unable to start postgresql

John Iliffe writes: > When the programme exited it left another postmaster.pid file so I deleted > that one too. You haven't shown us the program actually exiting, and basically the only way to get the postmaster to exit without removing its pid file is to kill -9 it.

Re: [GENERAL] Unable to start postgresql

Yes, that file was present, so I deleted it. Attempted to restart and got the same result: LOG: could not bind IPv4 socket: Cannot assign requested address HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry. LOG: database system was interrupted;

Re: [GENERAL] Unable to start postgresql

On 03/07/2017 08:17 PM, John Iliffe wrote: I was unable to get postgres started so I did a very basic compile/install to test it. The configuration line was: ./configure --prefix=/usr/postgres-9.6.2 Then I ran make which completed as expected: make[1]:

Re: [GENERAL] Unable to start postgresql

John Iliffe writes: > Now, running as user postgres I try and start as stated in the manual > postgres -D /usr/pgsql_tablespaces > The result is: > [postgres@prod04 postgresql-9.6.2]$ postgres -D /usr/pgsql_tablespaces > LOG: could not bind IPv4 socket: Cannot assign

Re: [GENERAL] Unable to start postgresql

On Tue, Mar 7, 2017 at 11:17 PM, John Iliffe wrote: > I was unable to get postgres started so I did a very basic compile/install > to test it. The configuration line was: > > ./configure --prefix=/usr/postgres-9.6.2 > > > Then I ran make

Re: [GENERAL] unable to start postgresql server services (Windows XP/Professional/Service Pack3)

On Tue, Apr 20, 2010 at 11:47 PM, Yan Cheng CHEOK ycch...@yahoo.com wrote: Using the command solve the problem. Bravo! D:\Program Files\PostgreSQL\8.4\binpg_resetxlog -f D:\Program Files\PostgreSQL\8.4\data Just so you know you may (likely will) lose some transactions. -- Sent via

Re: [GENERAL] unable to start postgresql server services (Windows XP/Professional/Service Pack3)

Oh. Then do you know any way I may recover, without losing any transaction? Thanks and Regards Yan Cheng CHEOK --- On Wed, 4/21/10, Scott Marlowe scott.marl...@gmail.com wrote: From: Scott Marlowe scott.marl...@gmail.com Subject: Re: [GENERAL] unable to start postgresql server services

Re: [GENERAL] unable to start postgresql server services (Windows XP/Professional/Service Pack3)

On Wed, Apr 21, 2010 at 1:38 AM, Yan Cheng CHEOK ycch...@yahoo.com wrote: Oh. Then do you know any way I may recover, without losing any transaction? Not in your situation, you did the best you could and got the db back up. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org)

Re: [GENERAL] unable to start postgresql server services (Windows XP/Professional/Service Pack3)

And the log message (D:\Program Files\PostgreSQL\8.4\data\pg_log) is as follow : 2010-04-21 13:34:58 MYTLOG: database system was interrupted; last known up at 2010-04-08 14:26:26 MYT 2010-04-21 13:34:58 MYTLOG: could not open file pg_xlog/000100090041 (log file 9, segment 65): No

Re: [GENERAL] unable to start postgresql server services (Windows XP/Professional/Service Pack3)

Using the command solve the problem. Bravo! D:\Program Files\PostgreSQL\8.4\binpg_resetxlog -f D:\Program Files\PostgreSQL\8.4\data Transaction log reset Thanks and Regards Yan Cheng CHEOK --- On Wed, 4/21/10, Yan Cheng CHEOK ycch...@yahoo.com wrote: From: Yan Cheng CHEOK ycch...@yahoo.com

Re: [GENERAL] Unable to Start PostgreSQL 8.1.4 on Windows XP

Ludwig Isaac Lim wrote on 15.08.2006 18:05: Searching the web using google gives me the following information about error 1063: Error code 1063: ERROR_FAILED_SERVICE_CONTROLLER_CONNECT - The service process could not connect to the service controller. (from

Re: [GENERAL] Unable to Start PostgreSQL 8.1.4 on Windows XP

Hi Thomas : --- Thomas Kellerer [EMAIL PROTECTED] wrote: Ludwig Isaac Lim wrote on 15.08.2006 18:05: Searching the web using google gives me the following information about error 1063: Error code 1063: ERROR_FAILED_SERVICE_CONTROLLER_CONNECT - I had a similar issue several weeks ago.