Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade

OK, there are some logs there, most have old date/time stamps. But there
is one with today's time on it, but all it has is week-old data, likely
from near the time I did the Ubuntu upgrade. The following entry makes
me worry (it is about 2/3 of the way down...)

2018-03-22 10:14:28 MDT LOG:  database system was not properly shut
down; automatic recovery in progress
2018-03-22 10:14:28 MDT LOG:  record with zero length at 0/16178450

2018-03-18 16:41:12 MDT LOG:  received fast shutdown request
2018-03-18 16:41:12 MDT LOG:  aborting any active transactions
2018-03-18 16:41:12 MDT LOG:  autovacuum launcher shutting down
2018-03-18 16:41:12 MDT LOG:  shutting down
2018-03-18 16:41:12 MDT LOG:  database system is shut down
2018-03-19 17:00:41 MDT LOG:  database system was shut down at
2018-03-18 16:41:12 MDT
2018-03-19 17:00:41 MDT FATAL:  the database system is starting up
2018-03-19 17:00:41 MDT LOG:  incomplete startup packet
2018-03-19 17:00:41 MDT FATAL:  the database system is starting up
2018-03-19 17:00:42 MDT FATAL:  the database system is starting up
2018-03-19 17:00:42 MDT LOG:  MultiXact member wraparound protections
are now enabled
2018-03-19 17:00:42 MDT LOG:  database system is ready to accept connections
2018-03-19 17:00:42 MDT LOG:  autovacuum launcher started
2018-03-19 18:10:24 MDT LOG:  received fast shutdown request
2018-03-19 18:10:24 MDT LOG:  aborting any active transactions
2018-03-19 18:10:24 MDT LOG:  autovacuum launcher shutting down
2018-03-19 18:10:24 MDT LOG:  shutting down
2018-03-19 18:10:24 MDT LOG:  database system is shut down
2018-03-21 08:08:50 MDT LOG:  incomplete startup packet
2018-03-21 08:08:50 MDT LOG:  database system was shut down at
2018-03-19 18:10:24 MDT
2018-03-21 08:08:50 MDT FATAL:  the database system is starting up
2018-03-21 08:08:51 MDT FATAL:  the database system is starting up
2018-03-21 08:08:51 MDT FATAL:  the database system is starting up
2018-03-21 08:08:52 MDT LOG:  MultiXact member wraparound protections
are now enabled
2018-03-21 08:08:52 MDT LOG:  database system is ready to accept connections
2018-03-21 08:08:52 MDT LOG:  autovacuum launcher started
2018-03-22 10:14:22 MDT LOG:  incomplete startup packet
2018-03-22 10:14:22 MDT FATAL:  the database system is starting up
2018-03-22 10:14:22 MDT LOG:  database system was interrupted; last
known up at 2018-03-21 08:08:51 MDT
2018-03-22 10:14:22 MDT FATAL:  the database system is starting up
2018-03-22 10:14:23 MDT FATAL:  the database system is starting up
2018-03-22 10:14:23 MDT FATAL:  the database system is starting up
2018-03-22 10:14:24 MDT FATAL:  the database system is starting up
2018-03-22 10:14:24 MDT FATAL:  the database system is starting up
2018-03-22 10:14:25 MDT FATAL:  the database system is starting up
2018-03-22 10:14:25 MDT FATAL:  the database system is starting up
2018-03-22 10:14:26 MDT FATAL:  the database system is starting up
2018-03-22 10:14:26 MDT FATAL:  the database system is starting up
2018-03-22 10:14:27 MDT FATAL:  the database system is starting up
2018-03-22 10:14:27 MDT LOG:  incomplete startup packet
2018-03-22 10:14:28 MDT LOG:  database system was not properly shut
down; automatic recovery in progress
2018-03-22 10:14:28 MDT LOG:  record with zero length at 0/16178450
2018-03-22 10:14:28 MDT LOG:  redo is not required
2018-03-22 10:14:28 MDT LOG:  MultiXact member wraparound protections
are now enabled
2018-03-22 10:14:28 MDT LOG:  database system is ready to accept connections
2018-03-22 10:14:28 MDT LOG:  autovacuum launcher started
2018-03-22 11:15:02 MDT LOG:  received fast shutdown request
2018-03-22 11:15:02 MDT LOG:  aborting any active transactions
2018-03-22 11:15:02 MDT LOG:  autovacuum launcher shutting down
2018-03-22 11:15:02 MDT LOG:  shutting down
2018-03-22 11:15:02 MDT LOG:  database system is shut down
2018-03-22 11:15:03 MDT LOG:  database system was shut down at
2018-03-22 11:15:02 MDT
2018-03-22 11:15:03 MDT LOG:  MultiXact member wraparound protections
are now enabled
2018-03-22 11:15:03 MDT LOG:  database system is ready to accept connections
2018-03-22 11:15:03 MDT LOG:  autovacuum launcher started
2018-03-22 11:15:03 MDT LOG:  incomplete startup packet

Ken Beck
Liberty, Utah, USA

On 03/27/2018 12:04 PM, Joshua D. Drake wrote:
> On 03/27/2018 11:00 AM, Ken Beck wrote:
>> And, looking for log files, I find none.
>
> Nothing in /var/log/postgresql or /var/lib/postgresql/9.3/main/pg_log?
>
> JD
> --
>
> Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
> ***  A fault and talent of mine is to tell it exactly how it is.  ***
> PostgreSQL centered full stack support, consulting and development.
> Advocate: @amplifypostgres || Learn: https://postgresconf.org
> *****     Unless otherwise stated, opinions are my own.   *****
>