Bug 1167105

Summary: [abrt] postgresql-server: errfinish(): postgres killed by SIGABRT
Product: [Fedora] Fedora Reporter: ell1e <el>
Component: postgresqlAssignee: Pavel Raiskup <praiskup>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: devrim, hhorak, jmlich, jstanek, praiskup, tgl, xiangjihan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9038199fea28c8f4ee093eaac1919b6edd369446
Whiteboard: abrt_hash:80fd2d181c6c1296ee663b9cdbfcbf317544d610
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-24 11:19:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description ell1e 2014-11-23 17:13:24 UTC 
Version-Release number of selected component:
postgresql-server-9.3.5-4.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        'postgres: checkpointer process   ' '' '' '' '' '' '' '' '' '' '' '' '' '' ''
crash_function: errfinish
executable:     /usr/bin/postgres
kernel:         3.17.3-300.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1002

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 errfinish at elog.c:562
 #3 UpdateControlFile at xlog.c:3757
 #4 CreateCheckPoint at xlog.c:6856
 #5 ShutdownXLOG at xlog.c:6641
 #6 CheckpointerMain at checkpointer.c:413
 #7 AuxiliaryProcessMain at bootstrap.c:431
 #8 StartChildProcess at postmaster.c:4977
 #9 reaper at postmaster.c:2580
 #11 __select_nocancel at ../sysdeps/unix/syscall-template.S:81
 #12 ServerLoop at postmaster.c:1546

Potential duplicate: bug 1039605
Comment 1 ell1e 2014-11-23 17:13:27 UTC 
Created attachment 960471 [details]
File: backtrace
Comment 2 ell1e 2014-11-23 17:13:29 UTC 
Created attachment 960472 [details]
File: build_ids
Comment 3 ell1e 2014-11-23 17:13:30 UTC 
Created attachment 960473 [details]
File: cgroup
Comment 4 ell1e 2014-11-23 17:13:31 UTC 
Created attachment 960474 [details]
File: core_backtrace
Comment 5 ell1e 2014-11-23 17:13:32 UTC 
Created attachment 960475 [details]
File: dso_list
Comment 6 ell1e 2014-11-23 17:13:33 UTC 
Created attachment 960476 [details]
File: environ
Comment 7 ell1e 2014-11-23 17:13:34 UTC 
Created attachment 960477 [details]
File: limits
Comment 8 ell1e 2014-11-23 17:13:36 UTC 
Created attachment 960478 [details]
File: maps
Comment 9 ell1e 2014-11-23 17:13:37 UTC 
Created attachment 960479 [details]
File: open_fds
Comment 10 ell1e 2014-11-23 17:13:38 UTC 
Created attachment 960480 [details]
File: proc_pid_status
Comment 11 ell1e 2014-11-23 17:13:41 UTC 
Created attachment 960481 [details]
File: var_log_messages
Comment 12 Tom Lane 2014-11-23 17:30:01 UTC 
This is the same crash location as in bug 1039605, and as there, a PANIC is expected if the pg_control file disappeared.  The question is what did that ...
Comment 13 ell1e 2014-11-23 20:29:49 UTC 
Well I send SIGTERM to the postmaster and shortly after removed the database directory. This might explain why a file might be gone (: I guess it's possibly a user error but the reporting tool was eager to report it, so I went ahead.
Comment 14 Pavel Raiskup 2014-11-24 11:19:30 UTC 
(In reply to Jonas Thiem from comment #13)
> Well I send SIGTERM to the postmaster and shortly after removed the database
> directory.  This might explain why a file might be gone (: possibly a user
> error but the reporting tool was eager to report it, so I went ahead.

I'm closing as duplicate then, but thanks for the bug-report, Jonas.  And
thanks Tom for looking at this.

Pavel

*** This bug has been marked as a duplicate of bug 1039605 ***
Comment 15 Pavel Raiskup 2017-11-09 18:02:45 UTC 
*** Bug 1421544 has been marked as a duplicate of this bug. ***