pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedHow to analyze a core dump
6+ messages / 3 participants
[nested] [flat]
* How to analyze a core dump
@ 2020-11-02 16:41 S Bob <sbob@quadratum-braccas.com>
2020-11-02 16:55 ` Re: How to analyze a core dump Peter Geoghegan <pg@bowt.ie>
0 siblings, 1 reply; 6+ messages in thread
From: S Bob @ 2020-11-02 16:41 UTC (permalink / raw)
To: pgsql-admin
All;
I have this message in the /var/log/message log on a server running
PostgreSQL:
ID 603404 kern.notice] NOTICE: core_log: postgres[20995] core dumped:
/var/coredumps/core_smffnsdb3_postgres_1000_1500_1603426561_20995
and this in the postgresql log:
2020-10-23 04:17:40 GMT [5588]:[21-1] 5df751a6.15d4 >LOG: server
process (PID 20995) was terminated by signal 10
How do I determine the root cause?
Thanks in advance
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: How to analyze a core dump
2020-11-02 16:41 How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
@ 2020-11-02 16:55 ` Peter Geoghegan <pg@bowt.ie>
2020-11-02 17:04 ` Re: How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
0 siblings, 1 reply; 6+ messages in thread
From: Peter Geoghegan @ 2020-11-02 16:55 UTC (permalink / raw)
To: S Bob <sbob@quadratum-braccas.com>; +Cc: pgsql-admin
On Mon, Nov 2, 2020 at 8:41 AM S Bob <sbob@quadratum-braccas.com> wrote:
> 2020-10-23 04:17:40 GMT [5588]:[21-1] 5df751a6.15d4 >LOG: server
> process (PID 20995) was terminated by signal 10
>
> How do I determine the root cause?
Is signal 10 SIGBUS on your platform? Perhaps check the relevant man
page on your platform -- "man signal.7" works for me here.
What CPU architecture and operating system are you using?
--
Peter Geoghegan
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: How to analyze a core dump
2020-11-02 16:41 How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
2020-11-02 16:55 ` Re: How to analyze a core dump Peter Geoghegan <pg@bowt.ie>
@ 2020-11-02 17:04 ` S Bob <sbob@quadratum-braccas.com>
2020-11-02 18:04 ` Re: How to analyze a core dump Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 6+ messages in thread
From: S Bob @ 2020-11-02 17:04 UTC (permalink / raw)
To: Peter Geoghegan <pg@bowt.ie>; +Cc: pgsql-admin
On 11/2/20 9:55 AM, Peter Geoghegan wrote:
> On Mon, Nov 2, 2020 at 8:41 AM S Bob <sbob@quadratum-braccas.com> wrote:
>> 2020-10-23 04:17:40 GMT [5588]:[21-1] 5df751a6.15d4 >LOG: server
>> process (PID 20995) was terminated by signal 10
>>
>> How do I determine the root cause?
> Is signal 10 SIGBUS on your platform? Perhaps check the relevant man
> page on your platform -- "man signal.7" works for me here.
>
> What CPU architecture and operating system are you using?
32 bit, Solaris 10
(ugh)
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: How to analyze a core dump
2020-11-02 16:41 How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
2020-11-02 16:55 ` Re: How to analyze a core dump Peter Geoghegan <pg@bowt.ie>
2020-11-02 17:04 ` Re: How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
@ 2020-11-02 18:04 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-11-02 18:10 ` Re: How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
0 siblings, 1 reply; 6+ messages in thread
From: Tom Lane @ 2020-11-02 18:04 UTC (permalink / raw)
To: S Bob <sbob@quadratum-braccas.com>; +Cc: Peter Geoghegan <pg@bowt.ie>; pgsql-admin
S Bob <sbob@quadratum-braccas.com> writes:
> On 11/2/20 9:55 AM, Peter Geoghegan wrote:
>> Is signal 10 SIGBUS on your platform? Perhaps check the relevant man
>> page on your platform -- "man signal.7" works for me here.
>> What CPU architecture and operating system are you using?
> 32 bit, Solaris 10
Solaris should be enough like other Unixen to presume that SIGBUS is 10.
However, that doesn't get you far towards finding a root cause.
Since you have a core file, maybe you could extract a stack trace
from it? We have some suggestions at
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
although I'm afraid that's pretty gdb-specific, and Solaris probably
has different debugging tools.
What PG version are you running, exactly?
regards, tom lane
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: How to analyze a core dump
2020-11-02 16:41 How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
2020-11-02 16:55 ` Re: How to analyze a core dump Peter Geoghegan <pg@bowt.ie>
2020-11-02 17:04 ` Re: How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
2020-11-02 18:04 ` Re: How to analyze a core dump Tom Lane <tgl@sss.pgh.pa.us>
@ 2020-11-02 18:10 ` S Bob <sbob@quadratum-braccas.com>
2020-11-02 18:19 ` Re: How to analyze a core dump Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 6+ messages in thread
From: S Bob @ 2020-11-02 18:10 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Peter Geoghegan <pg@bowt.ie>; pgsql-admin
On 11/2/20 11:04 AM, Tom Lane wrote:
> S Bob <sbob@quadratum-braccas.com> writes:
>> On 11/2/20 9:55 AM, Peter Geoghegan wrote:
>>> Is signal 10 SIGBUS on your platform? Perhaps check the relevant man
>>> page on your platform -- "man signal.7" works for me here.
>>> What CPU architecture and operating system are you using?
>> 32 bit, Solaris 10
> Solaris should be enough like other Unixen to presume that SIGBUS is 10.
> However, that doesn't get you far towards finding a root cause.
>
> Since you have a core file, maybe you could extract a stack trace
> from it? We have some suggestions at
>
> https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
>
> although I'm afraid that's pretty gdb-specific, and Solaris probably
> has different debugging tools.
>
> What PG version are you running, exactly?
This client is running Postgres version 9.0.4
I'll have a look at the link you sent, thanks!
>
> regards, tom lane
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: How to analyze a core dump
2020-11-02 16:41 How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
2020-11-02 16:55 ` Re: How to analyze a core dump Peter Geoghegan <pg@bowt.ie>
2020-11-02 17:04 ` Re: How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
2020-11-02 18:04 ` Re: How to analyze a core dump Tom Lane <tgl@sss.pgh.pa.us>
2020-11-02 18:10 ` Re: How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
@ 2020-11-02 18:19 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 6+ messages in thread
From: Tom Lane @ 2020-11-02 18:19 UTC (permalink / raw)
To: S Bob <sbob@quadratum-braccas.com>; +Cc: Peter Geoghegan <pg@bowt.ie>; pgsql-admin
S Bob <sbob@quadratum-braccas.com> writes:
> On 11/2/20 11:04 AM, Tom Lane wrote:
>> What PG version are you running, exactly?
> This client is running Postgres version 9.0.4
TBH, the first thing you should do is upgrade to a supported PG
version, or failing that, at least the last minor version in
the 9.0 branch (9.0.23). It's highly likely that you are hitting
a bug that was fixed years ago.
regards, tom lane
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2020-11-02 18:19 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-11-02 16:41 How to analyze a core dump S Bob <sbob@quadratum-braccas.com>
2020-11-02 16:55 ` Peter Geoghegan <pg@bowt.ie>
2020-11-02 17:04 ` S Bob <sbob@quadratum-braccas.com>
2020-11-02 18:04 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-11-02 18:10 ` S Bob <sbob@quadratum-braccas.com>
2020-11-02 18:19 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox