Bug 617081

Summary: [abrt] crash in postgresql-server-8.4.4-1.fc13: raise: Process /usr/bin/postgres was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: ruslancusnir
Component: postgresqlAssignee: Tom Lane <tgl>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: devrim, hhorak, tgl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:198900ba065dcf92cce553849af2a37060cca6cd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-04 22:11:37 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

Description ruslancusnir 2010-07-22 07:01:34 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/postgres -D ./JIRADB
component: postgresql
crash_function: raise
executable: /usr/bin/postgres
global_uuid: 198900ba065dcf92cce553849af2a37060cca6cd
kernel: 2.6.33.6-147.fc13.x86_64
package: postgresql-server-8.4.4-1.fc13
rating: 4
reason: Process /usr/bin/postgres was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

Comment 1 ruslancusnir 2010-07-22 07:01:37 UTC
Created attachment 433606 [details]
File: backtrace

Comment 2 Tom Lane 2010-07-27 16:11:41 UTC
This is evidently a PANIC in ReadControlFile, but there's not enough information in the backtrace to guess at the reason.  There should have been a message printed on stderr though ... what did it say?

Comment 3 ruslancusnir 2010-10-04 22:11:37 UTC
Sorry, it was a migration of files problem.