Bug 617081 - [abrt] crash in postgresql-server-8.4.4-1.fc13: raise: Process /usr/bin/postgres was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in postgresql-server-8.4.4-1.fc13: raise: Process /usr/bin/postg...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: postgresql
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tom Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:198900ba065dcf92cce553849af...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-22 07:01 UTC by ruslancusnir
Modified: 2013-07-03 03:31 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-10-04 22:11:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (7.24 KB, text/plain)
2010-07-22 07:01 UTC, ruslancusnir 		no flags Details
View All

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.
Note You need to log in before you can comment on or make changes to this bug.