Bug 1299646

Summary: [abrt] postgresql-server: errfinish(): postgres killed by SIGABRT
Product: [Fedora] Fedora Reporter: Francisco de la Peña <fran>
Component: postgresqlAssignee: Pavel Raiskup <praiskup>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: devrim, fran, hhorak, jmlich83, jstanek, pkajaba, praiskup, tgl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5c2a4bb95eebd0b81527affa6e8850164df5020d
Whiteboard: abrt_hash:80fd2d181c6c1296ee663b9cdbfcbf317544d610;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-01 13:29:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Francisco de la Peña 2016-01-18 21:24:09 UTC 
Version-Release number of selected component:
postgresql-server-9.4.5-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        'postgres: checkpointer process   ' '' '' '' '' '' '' ''
crash_function: errfinish
executable:     /usr/bin/postgres
global_pid:     8936
kernel:         4.2.8-libre.300.fc23.gnu.x86_64
runlevel:       N 5
type:           CCpp
uid:            26

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 errfinish at elog.c:572
 #3 UpdateControlFile at xlog.c:4659
 #4 CreateCheckPoint at xlog.c:8162
 #5 ShutdownXLOG at xlog.c:7943
 #6 CheckpointerMain at checkpointer.c:413
 #7 AuxiliaryProcessMain at bootstrap.c:432
 #8 StartChildProcess at postmaster.c:5243
 #9 reaper at postmaster.c:2718
 #11 __select_nocancel at ../sysdeps/unix/syscall-template.S:84
 #12 ServerLoop at postmaster.c:1642

Potential duplicate: bug 1167105
Comment 1 Francisco de la Peña 2016-01-18 21:24:15 UTC 
Created attachment 1115968 [details]
File: backtrace
Comment 2 Francisco de la Peña 2016-01-18 21:24:16 UTC 
Created attachment 1115969 [details]
File: cgroup
Comment 3 Francisco de la Peña 2016-01-18 21:24:18 UTC 
Created attachment 1115970 [details]
File: core_backtrace
Comment 4 Francisco de la Peña 2016-01-18 21:24:19 UTC 
Created attachment 1115971 [details]
File: dso_list
Comment 5 Francisco de la Peña 2016-01-18 21:24:20 UTC 
Created attachment 1115972 [details]
File: environ
Comment 6 Francisco de la Peña 2016-01-18 21:24:22 UTC 
Created attachment 1115973 [details]
File: limits
Comment 7 Francisco de la Peña 2016-01-18 21:24:23 UTC 
Created attachment 1115974 [details]
File: maps
Comment 8 Francisco de la Peña 2016-01-18 21:24:24 UTC 
Created attachment 1115975 [details]
File: mountinfo
Comment 9 Francisco de la Peña 2016-01-18 21:24:26 UTC 
Created attachment 1115976 [details]
File: namespaces
Comment 10 Francisco de la Peña 2016-01-18 21:24:27 UTC 
Created attachment 1115977 [details]
File: open_fds
Comment 11 Francisco de la Peña 2016-01-18 21:24:28 UTC 
Created attachment 1115978 [details]
File: proc_pid_status
Comment 12 Francisco de la Peña 2016-01-18 21:24:30 UTC 
Created attachment 1115979 [details]
File: var_log_messages
Comment 13 Tom Lane 2016-01-18 21:52:52 UTC 
What would actually be useful here is the tail end of the postmaster log --- do you have that?

The stack trace says that the failure occurred while trying to write pg_control during a database shutdown.  An error in that would lead to a PANIC exit, which does abort(), so the SIGABRT in itself is neither surprising nor indicative of a bug.  What would be interesting to know is why the write failed --- out of disk space? somebody mangled the permissions on the file? who knows?  ... but there should be an entry in the postmaster log reporting what errno we got.
Comment 14 Francisco de la Peña 2016-02-01 13:29:14 UTC 
I've read the log, however the postmaster log didn't have relevant shutdown information. There was enough disk space and the issue didn't happen again so far. I'll reopen if this happens again with relevant data.