Re: server will not start (Debian) - Mailing list pgsql-general

From stan
Subject Re: server will not start (Debian)
Date
Msg-id 20191210133635.GA24804@panix.com
Whole thread Raw
In response to server will not start (Debian)  (stan <stanb@panix.com>)
List pgsql-general
On Tue, Dec 10, 2019 at 06:48:23AM -0500, stan wrote:
> I just went to do soem work on our test/sandbox instance. I had upgraded
> this ssytem to V12 a few days agao. I found that it was not running:
> 
> Here is the last thing in the log:
> 
> 2019-12-06 14:16:06.149 EST [3764] LOG:  received fast shutdown request
> 2019-12-06 14:16:06.154 EST [3764] LOG:  aborting any active transactions
> 2019-12-06 14:16:06.160 EST [3764] LOG:  background worker "logical
> replication launcher" (PID 3771) exited with exit code 1
> 2019-12-06 14:16:06.162 EST [3766] LOG:  shutting down
> 2019-12-06 14:16:06.204 EST [3764] LOG:  database system is shut down
> 
> 
> This was in the logfile that was one rotation back. The current one is
> zero bytes:
> 
> pg_lsclsuters shows:
> 
> Ver Cluster Port Status Owner    Data directory              Log file
> 12  main    5432 down   postgres /var/lib/postgresql/12/main
> /var/log/postgresql/postgresql-12-main.log
> 
> systemctl status postgresql shows:
> 
> root@stantest:/var/log/postgresql# systemctl status postgresql
> ● postgresql.service - PostgreSQL RDBMS
>    Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor
>    prese
>   Active: active (exited) since Fri 2019-12-06 14:22:13 EST; 3 days ago
> Process: 371 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
> Process: 5555 ExecReload=/bin/true (code=exited,
> status=0/SUCCESS)
> Main PID: 371 (code=exited, status=0/SUCCESS)
> 
> Dec 10 06:41:19 stantest systemd[1]: Reloading PostgreSQL RDBMS.
> Dec 10 06:41:19 stantest systemd[1]: Reloaded PostgreSQL RDBMS.
> Warning: Journal has been rotated since unit was started. Log output is incomple
> 
> What do I need to do to get it started AND fix whatever caused this
> unexpected shutdown?
> 
> 
More info:

As user posgres I cna start the server with:

/usr/lib/postgresql/12/bin/postgres -D /var/lib/postgresql/12/main -c
config_file=/etc/postgresql/12/main/postgresql.conf

Then I can connect to it. But sysctl does not start the instance. 


I am also getting this error message:

/var/run/postgresql/12-main.pg_stat_tmp/global.tmp": No such file or
directory
2019-12-10 08:35:02.360 EST [786] LOG:  could not open temporary
statistics file "/var/run/postgresql/12-main.pg_stat_tmp/global.tmp": No
such file or directory

But if I create that directory manually I cna start the server,

As a reminder, this instance was recently upgarded from V11 to V12, if
thta is significant.



-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
                        -- Benjamin Franklin



pgsql-general by date:

Previous
From: Олег Самойлов
Date:
Subject: PostgreSQL vs PostgresQL
Next
From: Tom Lane
Date:
Subject: Re: tcp keep alive don't work when the backend is busy