Red Hat Bugzilla – Bug 1299646
[abrt] postgresql-server: errfinish(): postgres killed by SIGABRT
Last modified: 2016-02-01 08:29:14 EST
Version-Release number of selected component:
cmdline: 'postgres: checkpointer process ' '' '' '' '' '' '' ''
runlevel: N 5
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
Created attachment 1115968 [details]
Created attachment 1115969 [details]
Created attachment 1115970 [details]
Created attachment 1115971 [details]
Created attachment 1115972 [details]
Created attachment 1115973 [details]
Created attachment 1115974 [details]
Created attachment 1115975 [details]
Created attachment 1115976 [details]
Created attachment 1115977 [details]
Created attachment 1115978 [details]
Created attachment 1115979 [details]
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.
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.