Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process

From: Achilleas Mantzios <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
Date: 2024-06-17 05:14:07
Message-ID: a477773e-c7ad-4dae-bb79-525f51069949@cloud.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Στις 17/6/24 02:49, ο/η Veerendra Pulapa έγραψε:
> Dear Team,
>
> I am experiencing a segmentation fault issue with the postmaster
> process of our PostgreSQL database, and I am seeking your assistance.
> Below are the details of the error and our system configuration.
>
> *Issue Description*
> We encountered a segmentation fault in the postmaster process of our
> PostgreSQL instance. The relevant system log entry is as follows:
>
> *DB Logs:*
> LOG:  restartpoint starting: time
> LOG:  startup process (PID 21704) was terminated by signal 11:
> Segmentation fault
> LOG:  terminating any other active server processes
> LOG:  database system is shut down
> LOG:  starting PostgreSQL 13.2 on x86_64-pc-linux-gnu, compiled by gcc
> (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit
> LOG:  listening on IPv4 address "0.0.0.0", port 5432
> LOG:  listening on IPv6 address "::", port 5432
> LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
> LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
> LOG:  database system was interrupted while in recovery at log time
> 2024-06-16 19:37:48 +08
> HINT:  If this has occurred more than once some data might be
> corrupted and you might need to choose an earlier recovery target.

This runs as a primary right? The logs indicate that the postmaster had
already crashed and was trying to recover while it threw another segfault.

Give us some historical background of any events that happened in the
course of your installation that might be of any interest. Such as, how
often do you get the problem, how long are you having this problem, what
did change before the problem started to appear (software/hardware).

IME, such errors could be due to either faulty CPU or memory. I'd run a
memtest and run diagnostics (BIOS), check temperatures, etc

>
> *OS logs:*
> kernel: postmaster[7844]: segfault at 2dd736b ip 00000000004ddc75 sp
> 00007ffe0e9c3490 error 6 in postgres[400000+73e000]
>
> *PostgreSQL Version and Environment:*
> PostgreSQL Version: 13.2
> Operating System: rhel 7.9
> Kernel Version: 3.10.0-1160.118.1.el7.x86_64
> System Specifications: [32 vCPU, 250GB]
>
> Br,
> Veerendra Pulapa | Technical Consultant
> M: +91-9949349894 | www.ashnik.com <http://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>
>
>
> /
> /______________________________________________________________________________________/
> /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. /
> /
> /
> /

--
Achilleas Mantzios
IT DEV - HEAD
IT DEPT
Dynacom Tankers Mgmt (as agents only)

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alexander Lipatov 2024-06-17 10:49:53 Custom ordering operator for type xid
Previous Message Vijaykumar Jain 2024-06-17 05:10:00 Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process