Обсуждение: Postgres update 9.1 to 9.3 - error port 50432

On 1/30/2015 12:31 PM, Mauricio Tavares wrote:
> Personal greetings ...
>
> Anyone ever have used pg_upgrade ????
>
> I tried to use it, but is giving the error
>
>
> The following are the commands and the returned error.
>
>
> -bash-4.1$ /usr/pgsql-9.3/bin/pg_upgrade -b /usr/pgsql-9.1/bin -B /usr/pgsql-9.3/bin -d /var/lib/pgsql/9.1/data/ -D
/var/lib/pgsql/9.3/data/-o "-c  
> config_file=/var/lib/pgsql/9.1/data/postgresql.conf" -O "-c config_file=/var/lib/pgsql/9.3/data/postgresql.conf"
> Performing Consistency Checks
> -----------------------------
> Checking cluster versions ok
> Checking database user is a superuser ok
> Checking for prepared transactions ok
> Checking for reg* system OID user data types ok
> Checking for contrib/isn with bigint-passing mismatch ok
> Creating dump of global objects ok
> Creating dump of database schemas
> ok
>
> *failure*
> Consult the last few lines of "pg_upgrade_server.log" for
> the probable cause of the failure.
>
> connection to database failed: could not connect to server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket "/var/lib/pgsql/.s.PGSQL.50432"?
>
>
> could not connect to new postmaster started with the command:
> "/usr/pgsql-9.3/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/var/lib/pgsql/9.3/data/" -o "-p 50432 -b -c
autovacuum_multixact_freeze_max_age=2000000000-c  
> synchronous_commit=off -c fsync=off -c full_page_writes=off-c config_file=/var/lib/pgsql/9.3/data/postgresql.conf -c
listen_addresses=''-c unix_socket_permissions=0700 -c  
> unix_socket_directories='/var/lib/pgsql'" start
> Failure, exiting
> -bash-4.1$
>
>
> I've changed the configs postgres the door, but still gives error ....
>
> I tried to force the use of the door with the parameters -p and -P, however the error was the same.
>
> Has anyone experienced this situation ???
>
>
> Thanks for listening ..
Mauricio,

First off, and I'm not trying to say that you're inexperienced, but have you run an initdb on the new 9.3 instance? And
ifso, can you start that instance manually? If so and if  
the database refuses start manually, what's that error? Also, have you checked the pgstartup.log for 9.3 when using
pg_upgrade?Or even the daily log file in the 9.3 data/pg_log  
directory?
--
Jay

On 15-01-30 12:31 PM, Mauricio Tavares wrote:
> Personal greetings ...
>
> Anyone ever have used pg_upgrade ????
>
> I tried to use it, but is giving the error
>
>
> The following are the commands and the returned error.
>
>
> -bash-4.1$ /usr/pgsql-9.3/bin/pg_upgrade -b /usr/pgsql-9.1/bin -B
> /usr/pgsql-9.3/bin -d /var/lib/pgsql/9.1/data/ -D
> /var/lib/pgsql/9.3/data/ -o "-c
> config_file=/var/lib/pgsql/9.1/data/postgresql.conf" -O "-c
> config_file=/var/lib/pgsql/9.3/data/postgresql.conf"
> Performing Consistency Checks
> -----------------------------
> Checking cluster versions ok
> Checking database user is a superuser ok
> Checking for prepared transactions ok
> Checking for reg* system OID user data types ok
> Checking for contrib/isn with bigint-passing mismatch ok
> Creating dump of global objects ok
> Creating dump of database schemas
> ok
>
> *failure*
> Consult the last few lines of "pg_upgrade_server.log" for
> the probable cause of the failure.
>
> connection to database failed: could not connect to server: No such
> file or directory
> Is the server running locally and accepting
> connections on Unix domain socket "/var/lib/pgsql/.s.PGSQL.50432"?
>
>
> could not connect to new postmaster started with the command:
> "/usr/pgsql-9.3/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
> "/var/lib/pgsql/9.3/data/" -o "-p 50432 -b -c
> autovacuum_multixact_freeze_max_age=2000000000 -c
> synchronous_commit=off -c fsync=off -c full_page_writes=off-c
> config_file=/var/lib/pgsql/9.3/data/postgresql.conf -c
> listen_addresses='' -c unix_socket_permissions=0700 -c
> unix_socket_directories='/var/lib/pgsql'" start
> Failure, exiting
> -bash-4.1$
>
>
> I've changed the configs postgres the door, but still gives error ....
>
> I tried to force the use of the door with the parameters -p and -P,
> however the error was the same.
>
> Has anyone experienced this situation ???
>
>
> Thanks for listening ..

Hi,

Is there a backend running on port 50432 or is this a typo and it was
supposed to be 5432 in the above pg_upgrade command?

Ziggy

Ziggy Skalski wrote
>> connection to database failed: could not connect to server: No such
>> file or directory
>> Is the server running locally and accepting
>> connections on Unix domain socket "/var/lib/pgsql/.s.PGSQL.50432"?
> Is there a backend running on port 50432 or is this a typo and it was
> supposed to be 5432 in the above pg_upgrade command?

Ziggy:

I suggest you read the pg_upgrade documentation.

http://www.postgresql.org/docs/9.4/static/pgupgrade.html

Specifically the part where it says:

"Obviously, no one should be accessing the clusters during the upgrade.
pg_upgrade defaults to running servers on port 50432 to avoid unintended
client connections."

David J.




--
View this message in context:
http://postgresql.nabble.com/Postgres-update-9-1-to-9-3-error-port-50432-tp5836178p5836200.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.

Payal,


I checked the doors and are not occupied



--
View this message in context:
http://postgresql.nabble.com/Postgres-update-9-1-to-9-3-error-port-50432-tp5836178p5836201.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.

netstat -tlp
Conexões Internet Ativas (sem os servidores)
Proto Recv-Q Send-Q Local Address               Foreign Address
State       PID/Program name
tcp        0      0 *:sunrpc                    *:*
OUÇA       1070/rpcbind
tcp        0      0 *:ssh                       *:*
OUÇA       1283/sshd
tcp        0      0 localhost:ipp               *:*
OUÇA       1160/cupsd
tcp        0      0 localhost:smtp              *:*
OUÇA       1524/master
tcp        0      0 *:55847                     *:*
OUÇA       1088/rpc.statd
tcp        0      0 *:mysql                     *:*
OUÇA       1426/mysqld
tcp        0      0 *:sunrpc                    *:*
OUÇA       1070/rpcbind
tcp        0      0 *:http                      *:*
OUÇA       1556/httpd
tcp        0      0 *:ssh                       *:*
OUÇA       1283/sshd
tcp        0      0 localhost:ipp               *:*
OUÇA       1160/cupsd
tcp        0      0 localhost:smtp              *:*
OUÇA       1524/master
tcp        0      0 *:40680                     *:*
OUÇA       1088/rpc.statd



--
View this message in context:
http://postgresql.nabble.com/Postgres-update-9-1-to-9-3-error-port-50432-tp5836178p5836202.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.

Jay,

I checked the error recorded in the log ...

See the results ...


-----------------------------------------------------------------
  pg_upgrade run on Fri Jan 30 02:55:44 2015
-----------------------------------------------------------------

command: "/usr/pgsql-9.1/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/lib/pgsql/9.1/data/" -o "-p 5433 -b -c
config_file=/var/lib/pgsql/9.1/data/postgresql.conf -c listen_addresses=''
-c unix_socket_permissions=0700 -c unix_socket_directory='/var/lib/pgsql'"
start >> "pg_upgrade_server.log" 2>&1
esperando o servidor iniciar....feito
servidor iniciado


command: "/usr/pgsql-9.1/bin/pg_ctl" -w -D "/var/lib/pgsql/9.1/data/" -o "-c
config_file=/var/lib/pgsql/9.1/data/postgresql.conf"  stop >>
"pg_upgrade_server.log" 2>&1
esperando o servidor desligar....feito
servidor está parado


command: "/usr/pgsql-9.3/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/var/lib/pgsql/9.3/data/" -o "-p 5432 -b -c
autovacuum_multixact_freeze_max_age=2000000000  -c synchronous_commit=off -c
fsync=off -c full_page_writes=off-c
config_file=/var/lib/pgsql/9.3/data/postgresql.conf -c listen_addresses=''
-c unix_socket_permissions=0700 -c unix_socket_directories='/var/lib/pgsql'"
start >> "pg_upgrade_server.log" 2>&1
esperando o servidor iniciar....FATAL:  parâmetro "full_page_writes" requer
um valor booleano
....parou de esperar
pg_ctl: não pode iniciar o servidor
Examine o arquivo de log.




--
View this message in context:
http://postgresql.nabble.com/Postgres-update-9-1-to-9-3-error-port-50432-tp5836178p5836203.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.

On 15-01-30 02:28 PM, David G Johnston wrote:
> Ziggy Skalski wrote
>>> connection to database failed: could not connect to server: No such
>>> file or directory
>>> Is the server running locally and accepting
>>> connections on Unix domain socket "/var/lib/pgsql/.s.PGSQL.50432"?
>> Is there a backend running on port 50432 or is this a typo and it was
>> supposed to be 5432 in the above pg_upgrade command?
> Ziggy:
>
> I suggest you read the pg_upgrade documentation.
>
> http://www.postgresql.org/docs/9.4/static/pgupgrade.html
>
> Specifically the part where it says:
>
> "Obviously, no one should be accessing the clusters during the upgrade.
> pg_upgrade defaults to running servers on port 50432 to avoid unintended
> client connections."
>
> David J.
>
>
>

Ah ok, I usually specify the ports when running pg_upgrade so didn't run
into that error message before :)

Z

On 1/30/2015 2:44 PM, MauricioLeite wrote:
> Jay,
>
> I checked the error recorded in the log ...
>
> See the results ...
>
>
> -----------------------------------------------------------------
>    pg_upgrade run on Fri Jan 30 02:55:44 2015
> -----------------------------------------------------------------
>
> command: "/usr/pgsql-9.1/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
> "/var/lib/pgsql/9.1/data/" -o "-p 5433 -b -c
> config_file=/var/lib/pgsql/9.1/data/postgresql.conf -c listen_addresses=''
> -c unix_socket_permissions=0700 -c unix_socket_directory='/var/lib/pgsql'"
> start >> "pg_upgrade_server.log" 2>&1
> esperando o servidor iniciar....feito
> servidor iniciado
>
>
> command: "/usr/pgsql-9.1/bin/pg_ctl" -w -D "/var/lib/pgsql/9.1/data/" -o "-c
> config_file=/var/lib/pgsql/9.1/data/postgresql.conf"  stop >>
> "pg_upgrade_server.log" 2>&1
> esperando o servidor desligar....feito
> servidor está parado
>
>
> command: "/usr/pgsql-9.3/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
> "/var/lib/pgsql/9.3/data/" -o "-p 5432 -b -c
> autovacuum_multixact_freeze_max_age=2000000000  -c synchronous_commit=off -c
> fsync=off -c full_page_writes=off-c
> config_file=/var/lib/pgsql/9.3/data/postgresql.conf -c listen_addresses=''
> -c unix_socket_permissions=0700 -c unix_socket_directories='/var/lib/pgsql'"
> start >> "pg_upgrade_server.log" 2>&1
> esperando o servidor iniciar....FATAL:  parâmetro "full_page_writes" requer
> um valor booleano
> ....parou de esperar
> pg_ctl: não pode iniciar o servidor
> Examine o arquivo de log.
>
>
>
>
> --
> View this message in context:
http://postgresql.nabble.com/Postgres-update-9-1-to-9-3-error-port-50432-tp5836178p5836203.html
> Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
>
>
Well, I'm assuming you see the error immediately above. You've got a bad parameter specified in your configuration for
full_page_writes.That's why the 9.3 instance is refusing to  
start for the pg_upgrade.

On Fri, Jan 30, 2015 at 02:55:02PM -0500, John Scalia wrote:
> Well, I'm assuming you see the error immediately above. You've got a
> bad parameter specified in your configuration for full_page_writes.
> That's why the 9.3 instance is refusing to start for the pg_upgrade.

Ah, he need to use the most recent version of 9.3.X --- it was a
pg_upgrade bug, I bet.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +