Re: server exiting abnormally after an OS upgrade

On 2015-02-13 15:29, Heikki Linnakangas wrote:
> On 02/13/2015 12:42 AM, Hugo Osvaldo Barrera wrote:
> >Here's the error which repeats ad infinitum:
> >
> > LOG: database system was shut down at 2015-02-12 14:41:29 GMT
> > LOG: database system is ready to accept connections
> > LOG: autovacuum launcher started
> > LOG: server process (PID 21205) was terminated by signal 6: Abort trap
> > LOG: terminating any other active server processes
> > WARNING: terminating connection because of crash of another server process
> > DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
> > HINT: In a moment you should be able to reconnect to the database and repeat your command.
>
> Can you get a core dump and a stack trace from it?
>
> - Heikki
>
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs

I'm slightly unsure how to do this - the docs give some references on how to
select a single process and attempt to attach gdb to it, but they seem to be
too short lived for me to do anything (<1s between errors), so I can't really
work with that.

Do you have any suggestions for this?

I'll try to enable core dumps in the meantime and get back to you on this,
thank,

--
Hugo Osvaldo Barrera
A: Because we read from top to bottom, left to right.
Q: Why should I start my reply below the quoted text?