Re: postgresql-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
>

It certainly took me a bit, but, with some help, I managed to get one:

(gdb) bt
#0 0x0000110a2815b92a in kill () at <stdin>:2
#1 0x0000110a28195119 in abort () at /usr/src/lib/libc/stdlib/abort.c:53
#2 0x0000110a2816a238 in memcpy (dst0=0xfb8d4, src0=0x6, length=0) at /usr/src/lib/libc/string/memcpy.c:65
#3 0x000011080cf8d1b1 in check_ip (raddr=0x110a899f7918, addr=0x110a899f9058, mask=0x110a899f9158) at hba.c:704
#4 0x000011080cf90a04 in check_hba (port=0x110a899f7800) at hba.c:1718
#5 0x000011080cf91d34 in hba_getauthmethod (port=0x110a899f7800) at hba.c:2256
#6 0x000011080cf88eb3 in ClientAuthentication (port=0x110a899f7800) at auth.c:307
#7 0x000011080d1edf5d in PerformAuthentication (port=0x110a899f7800) at postinit.c:223
#8 0x000011080d1eeae7 in InitPostgres (in_dbname=0x110af4508c00 "virtstart-dev", dboid=0,
username=0x110af4508be0 "virtstart-dev", out_dbname=0x0) at postinit.c:688
#9 0x000011080d0a3eb1 in PostgresMain (argc=1, argv=0x110af4508c20, dbname=0x110af4508c00 "virtstart-dev",
username=0x110af4508be0 "virtstart-dev") at postgres.c:3749
#10 0x000011080d033537 in BackendRun (port=Could not find the frame base for "BackendRun".
) at postmaster.c:4155
#11 0x000011080d032be8 in BackendStartup (port=0x110a899f7800) at postmaster.c:3829
#12 0x000011080d02f2d0 in ServerLoop () at postmaster.c:1597
#13 0x000011080d02e968 in PostmasterMain (argc=3, argv=0x7f7ffffd9658) at postmaster.c:1244
#14 0x000011080cf96dc8 in main (argc=Could not find the frame base for "main".
) at main.c:228
Current language: auto; currently asm

I stopped pg once it crashed and then bt'd the core. Does this help at all? Is
there something else I can provide?

Thanks,

--
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?