Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process

Dear,

I have run coredump in my current system but I want to understand the
coredump file and what went wrong with the signal 11 error(segmentation
fault)?

below are the coredump output:

/usr/bin/gdb /usr/pgsql-13/bin/postgres
/mnt/spool/abrt/ccpp-2024-06-18-11\:05\:00-7214/coredump
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/pgsql-13/bin/postgres...Reading symbols from
/usr/lib/debug/usr/pgsql-13/bin/postgres.debug...done.
done.

warning: core file may not match specified executable file.
[New LWP 7214]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `postgres: startup recovering
0000000100007C49000000A5'.
Program terminated with signal 11, Segmentation fault.
#0 0x00000000004ddc75 in _bt_swap_posting (newitem=newitem(at)entry=0x254bee8,
oposting=oposting(at)entry=0x7fc6c1b3ee20, postingoff=1) at nbtdedup.c:800
800 nbtdedup.c: No such file or directory.
Missing separate debuginfos, use: debuginfo-install
audit-libs-2.8.5-4.el7.x86_64 bzip2-libs-1.0.6-13.el7.x86_64
cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 elfutils-libelf-0.176-5.el7.x86_64
elfutils-libs-0.176-5.el7.x86_64 glibc-2.17-326.el7_9.x86_64
keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-55.el7_9.x86_64
libattr-2.4.46-13.el7.x86_64 libcap-2.22-11.el7.x86_64
libcap-ng-0.7.5-4.el7.x86_64 libcom_err-1.42.9-19.el7.x86_64
libgcc-4.8.5-44.el7.x86_64 libgcrypt-1.5.3-14.el7.x86_64
libgpg-error-1.12-3.el7.x86_64 libicu-50.2-4.el7_7.x86_64
libselinux-2.5-15.el7.x86_64 libstdc++-4.8.5-44.el7.x86_64
libxml2-2.9.1-6.el7_9.6.x86_64 lz4-1.8.3-1.el7.x86_64
nspr-4.35.0-1.el7_9.x86_64 nss-3.90.0-2.el7_9.x86_64
nss-softokn-freebl-3.90.0-6.el7_9.x86_64 nss-util-3.90.0-1.el7_9.x86_64
openldap-2.4.44-25.el7_9.x86_64 openssl-libs-1.0.2k-26.el7_9.x86_64
pam-1.1.8-23.el7.x86_64 pcre-8.32-17.el7.x86_64
systemd-libs-219-78.el7_9.9.x86_64 xz-libs-5.2.2-2.el7_9.x86_64
zlib-1.2.7-21.el7_9.x86_64
(gdb) bt
#0 0x00000000004ddc75 in _bt_swap_posting (newitem=newitem(at)entry=0x254bee8,
oposting=oposting(at)entry=0x7fc6c1b3ee20, postingoff=1) at nbtdedup.c:800
#1 0x00000000004ee423 in btree_xlog_insert (isleaf=isleaf(at)entry=true,
ismeta=ismeta(at)entry=false, posting=posting(at)entry=true,
record=record(at)entry=0x2529d48)
at nbtxlog.c:224
#2 0x00000000004eeea4 in btree_redo (record=0x2529d48) at nbtxlog.c:969
#3 0x000000000051caa5 in StartupXLOG () at xlog.c:7319
#4 0x00000000007197a1 in StartupProcessMain () at startup.c:204
#5 0x000000000052b94c in AuxiliaryProcessMain (argc=argc(at)entry=2,
argv=argv(at)entry=0x7ffd95f45740) at bootstrap.c:443
#6 0x000000000071679e in StartChildProcess (type=StartupProcess) at
postmaster.c:5492
#7 0x00000000007190e4 in PostmasterMain (argc=argc(at)entry=3,
argv=argv(at)entry=0x24f9280)
at postmaster.c:1404
#8 0x0000000000488bbd in main (argc=3, argv=0x24f9280) at main.c:210
(gdb)

Br,
Veerendra Pulapa | Technical Consultant
M: +91-9949349894 | www.ashnik.com

<https://www.linkedin.com/company/ashnik-pte-ltd/>
<https://www.facebook.com/AshnikBiz>
<https://www.youtube.com/user/ashnikbiz>
<https://www.instagram.com/ashnikbiz/> <https://twitter.com/Ashnikbiz>

On Mon, Jun 17, 2024 at 8:09 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:

> On Mon, 2024-06-17 at 18:30 +0530, Veerendra Pulapa wrote:
> > LOG: startup process (PID 21704) was terminated by signal 11:
> Segmentation fault
>
> If you want any support for that, you need to collect a core dump and
> generate a stack trace. Make sure that you have the debugging symbols
> installed.
>
> Also, we'd need to see the log messages *before* the lines you show.
> Everything
> since the start of the server.
>
> A segmentation fault is caused by a software bug. Since it happens during
> recovery, perhaps the WAL that is being replayed is corrupted and makes
> PostgreSQL fail.
>
> My recommendation is to restore your last good backup.
>
> Yours,
> Laurenz Albe
>

--

*________________________________________________________________________________________
*_This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s). If you are not the
rightful recipient of this email, please delete this email immediately and
inform the recipient. 
_
*
*