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

Postgresql create a core while trying log a message to syslog

From

"Demarest, Jamie"

Date:

11 March 2020, 21:24:45

Red Hat Enterprise Linux Server release 7.2 (Maipo)

postgres (PostgreSQL) 9.5.4

psql logging has been set up to log to syslog. When the syslog directory filled up psql trying to log to syslog cause psql to core.

Reading symbols from /opt/rh/rh-postgresql95/root/usr/bin/postgres...Reading symbols from /opt/rh/rh-postgresql95/root/usr/bin/postgres...(no debugging 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 ()

#7 0x00000000006563c2 in StartupProcessMain ()

#8 0x00000000004e4e8a in AuxiliaryProcessMain ()

#9 0x0000000000653800 in StartChildProcess ()

#10 0x0000000000655e44 in PostmasterMain ()

#11 0x0000000000469d3e in main ()

Core file can be supplied.

Thanks You,

Jamie Demarest

Saab Sensis Corporation

This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately.

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

From

Alvaro Herrera

Date:

12 March 2020, 01:14:57

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

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

From

Tom Lane

Date:

12 March 2020, 01:39:58

"Demarest, Jamie" <Jamie.Demarest@saabsensis.com> writes:
> 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. 

This looks more like a PANIC due to corrupt data than what you're
claiming the cause is.  I wonder whether the out-of-disk-space
problem had affected previous attempts to write to WAL.

            regards, tom lane

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

From

"Demarest, Jamie"

Date:

12 March 2020, 17:35:35

Alvaro,

Thank you for the quick response I am working with my team to get the debug installed so we can recreate the backtrace.


Thanks,
Jamie

-----Original Message-----
From: Alvaro Herrera [mailto:alvherre@2ndquadrant.com]
Sent: Thursday, March 12, 2020 8:27 AM
To: Demarest, Jamie
Cc: pgsql-bugs@lists.postgresql.org; Tamayo, Cristofer; Cornman, Melody
Subject: Re: Postgresql create a core while trying log a message to syslog

[ EXTERNAL EMAIL ]



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
-
This message is intended only for the addressee and may contain information that is company confidential or privileged.
Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms
Regulations(22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is
strictlyprohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering
tothe intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this
emailin error, please delete it, and advise the sender immediately.  
-

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

From

"Demarest, Jamie"

Date:

19 March 2020, 15:48:12

Alvaro,

Did you mean debuginfo-install rh-postgresql95-postgresql-server-9.5.4-1.el7.x86_64 of debuginfo-install
rh-postgresql95-postgresql-debuginfo-9.5.14-1.el7.x86_64.rpm

Thank you,
Jamie Demarest

-----Original Message-----
From: Alvaro Herrera [mailto:alvherre@2ndquadrant.com]
Sent: Thursday, March 12, 2020 8:27 AM
To: Demarest, Jamie
Cc: pgsql-bugs@lists.postgresql.org; Tamayo, Cristofer; Cornman, Melody
Subject: Re: Postgresql create a core while trying log a message to syslog

[ EXTERNAL EMAIL ]



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
-
This message is intended only for the addressee and may contain information that is company confidential or privileged.
Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms
Regulations(22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is
strictlyprohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering
tothe intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this
emailin error, please delete it, and advise the sender immediately.  
-

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

From

Alvaro Herrera

Date:

24 March 2020, 17:59:12

Jamie,

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

> Did you mean debuginfo-install rh-postgresql95-postgresql-server-9.5.4-1.el7.x86_64 of debuginfo-install
rh-postgresql95-postgresql-debuginfo-9.5.14-1.el7.x86_64.rpm

I merely copied the exact line that GDB gave you, which presumably
matches the executable package you already have installed.  If you try
to use a debuginfo package that does not *exactly* match the executable
you're running, it's going to give a bogus backtrace, if it gives
anything at all.

> This message is intended only for the addressee and may contain
> information that is company confidential or privileged.  Any technical
> data in this message may be exported only in accordance with the U.S.
> International Traffic in Arms Regulations (22 CFR Parts 120-130) or
> the Export Administration Regulations (15 CFR Parts 730-774).
> Unauthorized use is strictly prohibited and may be unlawful. If you
> are not the intended recipient, or the person responsible for
> delivering to the intended recipient, you should not read, copy,
> disclose or otherwise use this message. If you have received this
> email in error, please delete it, and advise the sender immediately. 

*shudder*  This is not a good thing to be posting to a public mailing
list, you know?

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