Re: Postgresql create a core while trying log a message to syslog

On 2020-Mar-11, Demarest, Jamie wrote:

> psql logging has been set up to log to syslog.  When the syslog directory filled up psql trying to log to syslog
causepsql to core.
 
> 
> Reading symbols from /opt/rh/rh-postgresql95/root/usr/bin/postgres...Reading symbols from
/opt/rh/rh-postgresql95/root/usr/bin/postgres...(nodebugging symbols found)...done.
 
> (no debugging symbols found)...done.
> [New LWP 7949]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `postgres: startup process   recovering 000000050000000000000017      '.
> Program terminated with signal 6, Aborted.
> #0  0x00007f385ebaf5f7 in raise () from /lib64/libc.so.6
> Missing separate debuginfos, use: debuginfo-install rh-postgresql95-postgresql-server-9.5.4-1.el7.x86_64
> (gdb) bt
> #0  0x00007f385ebaf5f7 in raise () from /lib64/libc.so.6
> #1  0x00007f385ebb0ce8 in abort () from /lib64/libc.so.6
> #2  0x0000000000797058 in errfinish ()
> #3  0x000000000079aa38 in elog_finish ()
> #4  0x0000000000495db4 in heap_xlog_update ()
> #5  0x000000000049d1af in heap_redo ()
> #6  0x00000000004d8117 in StartupXLOG ()

Hmm.  Please install debuginfo and get the backtrace again, as
instructed:

debuginfo-install rh-postgresql95-postgresql-server-9.5.4-1.el7.x86_64

Thanks

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services