Re: Upgrading error

From: chris navarroza <canavarroza(dot)work(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Upgrading error
Date: 2022-10-24 00:20:24
Message-ID: CADRdQ7oA+c5oW=GJV5U8CzF6J6cA_avqCMJOh3MxmqFhVH+4fQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

This is the log I got.
-----------------------------------------------------------------
pg_upgrade run on Mon Oct 24 07:41:13 2022
-----------------------------------------------------------------

command: "/usr/pgsql-12/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
"/home/dmartuser/pgdata/data" -o "-p 50432 -b -c
config_file=/var/lib/pgsql/12/data/postgresql.conf -c listen_addresses=''
-c unix_socket_permissions=0700 -c unix_socket_directories='/tmp'" start >>
"pg_upgrade_server.log" 2>&1
waiting for server to start....2022-10-23 23:41:13.458 GMT [107444] LOG:
skipping missing configuration file
"/home/dmartuser/pgdata/data/postgresql.auto.conf"
2022-10-24 07:41:13.459 PST [107444] LOG: starting PostgreSQL 12.9 on
x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat
8.5.0-4), 64-bit
2022-10-24 07:41:13.460 PST [107444] LOG: listening on Unix socket
"/tmp/.s.PGSQL.50432"
2022-10-24 07:41:13.486 PST [107444] LOG: redirecting log output to
logging collector process
2022-10-24 07:41:13.486 PST [107444] HINT: Future log output will appear
in directory "log".
stopped waiting
pg_ctl: could not start server
Examine the log output.

Thanks,

Chris Albert Navarroza
Information Technology Officer I
CTCO - ITDS - RDMD

On Mon, Oct 24, 2022 at 8:12 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> chris navarroza <canavarroza(dot)work(at)gmail(dot)com> writes:
> > could not connect to source postmaster started with the command:
> > "/usr/pgsql-12/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D
> > "/home/dmartuser/pgdata/data" -o "-p 50432 -b -c
> > config_file=/var/lib/pgsql/12/data/postgresql.conf -c listen_addresses=''
> > -c unix_socket_permissions=0700 -c unix_socket_directories='/tmp'" start
> > Failure, exiting
>
> Did you look into the postmaster log (pg_upgrade_server.log, here)
> to see what it thought about the problem? I'm guessing there's
> something that kept it from starting, but there's no evidence
> offered here about what.
>
> regards, tom lane
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2022-10-24 04:08:22 Re: synchronous streaming replication
Previous Message Tom Lane 2022-10-24 00:12:22 Re: Upgrading error