pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgres update 9.1 to 9.3 - error port 50432
11+ messages / 7 participants
[nested] [flat]
* Postgres update 9.1 to 9.3 - error port 50432
@ 2015-01-30 17:31 Mauricio Tavares <mfx1975@gmail.com>
0 siblings, 2 replies; 11+ messages in thread
From: Mauricio Tavares @ 2015-01-30 17:31 UTC (permalink / raw)
To: pgsql-admin
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 ..
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Postgres update 9.1 to 9.3 - error port 50432
@ 2015-01-30 18:29 John Scalia <jayknowsunix@gmail.com>
parent: Mauricio Tavares <mfx1975@gmail.com>
1 sibling, 1 reply; 11+ messages in thread
From: John Scalia @ 2015-01-30 18:29 UTC (permalink / raw)
To: Mauricio Tavares <mfx1975@gmail.com>; pgsql-admin
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 if so, 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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Postgres update 9.1 to 9.3 - error port 50432
@ 2015-01-30 19:05 Ziggy Skalski <zskalski@afilias.info>
parent: Mauricio Tavares <mfx1975@gmail.com>
1 sibling, 2 replies; 11+ messages in thread
From: Ziggy Skalski @ 2015-01-30 19:05 UTC (permalink / raw)
To: pgsql-admin
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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Postgres update 9.1 to 9.3 - error port 50432
@ 2015-01-30 19:10 Payal Singh <payal@omniti.com>
parent: Ziggy Skalski <zskalski@afilias.info>
1 sibling, 1 reply; 11+ messages in thread
From: Payal Singh @ 2015-01-30 19:10 UTC (permalink / raw)
To: Ziggy Skalski <zskalski@afilias.info>; +Cc: pgsql-admin
Try bringing up the new instance manually with pg_ctl first, then as the
postgres user connect to it with psql. Any error generated in the process
should give a better idea of what's wrong.
Also, I'm guessing you have already enabled trust authentication for
localhost for both new and old instances?
Payal Singh,
Database Administrator,
OmniTI Computer Consulting Inc.
Phone: 240.646.0770 x 253
On Fri, Jan 30, 2015 at 2:05 PM, Ziggy Skalski <zskalski@afilias.info>
wrote:
> 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
>
>
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Postgres update 9.1 to 9.3 - error port 50432
@ 2015-01-30 19:28 David G Johnston <david.g.johnston@gmail.com>
parent: Ziggy Skalski <zskalski@afilias.info>
1 sibling, 1 reply; 11+ messages in thread
From: David G Johnston @ 2015-01-30 19:28 UTC (permalink / raw)
To: pgsql-admin
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.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Postgres update 9.1 to 9.3 - error port 50432
@ 2015-01-30 19:34 MauricioLeite <mfx1975@gmail.com>
parent: Payal Singh <payal@omniti.com>
0 siblings, 1 reply; 11+ messages in thread
From: MauricioLeite @ 2015-01-30 19:34 UTC (permalink / raw)
To: pgsql-admin
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.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Postgres update 9.1 to 9.3 - error port 50432
@ 2015-01-30 19:35 MauricioLeite <mfx1975@gmail.com>
parent: MauricioLeite <mfx1975@gmail.com>
0 siblings, 0 replies; 11+ messages in thread
From: MauricioLeite @ 2015-01-30 19:35 UTC (permalink / raw)
To: pgsql-admin
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.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Postgres update 9.1 to 9.3 - error port 50432
@ 2015-01-30 19:44 MauricioLeite <mfx1975@gmail.com>
parent: John Scalia <jayknowsunix@gmail.com>
0 siblings, 1 reply; 11+ messages in thread
From: MauricioLeite @ 2015-01-30 19:44 UTC (permalink / raw)
To: pgsql-admin
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.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Postgres update 9.1 to 9.3 - error port 50432
@ 2015-01-30 19:48 Ziggy Skalski <zskalski@afilias.info>
parent: David G Johnston <david.g.johnston@gmail.com>
0 siblings, 0 replies; 11+ messages in thread
From: Ziggy Skalski @ 2015-01-30 19:48 UTC (permalink / raw)
To: pgsql-admin
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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Postgres update 9.1 to 9.3 - error port 50432
@ 2015-01-30 19:55 John Scalia <jayknowsunix@gmail.com>
parent: MauricioLeite <mfx1975@gmail.com>
0 siblings, 1 reply; 11+ messages in thread
From: John Scalia @ 2015-01-30 19:55 UTC (permalink / raw)
To: MauricioLeite <mfx1975@gmail.com>; pgsql-admin
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.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Postgres update 9.1 to 9.3 - error port 50432
@ 2015-01-30 21:09 Bruce Momjian <bruce@momjian.us>
parent: John Scalia <jayknowsunix@gmail.com>
0 siblings, 0 replies; 11+ messages in thread
From: Bruce Momjian @ 2015-01-30 21:09 UTC (permalink / raw)
To: John Scalia <jayknowsunix@gmail.com>; +Cc: MauricioLeite <mfx1975@gmail.com>; pgsql-admin
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. +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 11+ messages in thread
end of thread, other threads:[~2015-01-30 21:09 UTC | newest]
Thread overview: 11+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2015-01-30 17:31 Postgres update 9.1 to 9.3 - error port 50432 Mauricio Tavares <mfx1975@gmail.com>
2015-01-30 18:29 ` John Scalia <jayknowsunix@gmail.com>
2015-01-30 19:44 ` MauricioLeite <mfx1975@gmail.com>
2015-01-30 19:55 ` John Scalia <jayknowsunix@gmail.com>
2015-01-30 21:09 ` Bruce Momjian <bruce@momjian.us>
2015-01-30 19:05 ` Ziggy Skalski <zskalski@afilias.info>
2015-01-30 19:10 ` Payal Singh <payal@omniti.com>
2015-01-30 19:34 ` MauricioLeite <mfx1975@gmail.com>
2015-01-30 19:35 ` MauricioLeite <mfx1975@gmail.com>
2015-01-30 19:28 ` David G Johnston <david.g.johnston@gmail.com>
2015-01-30 19:48 ` Ziggy Skalski <zskalski@afilias.info>
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