Bug 712238
Summary: | [abrt] postgresql-server-9.0.4-2.fc15: errfinish: Process /usr/bin/postgres was killed by signal 6 (SIGABRT) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Trever Adams <trever> |
Component: | postgresql | Assignee: | Tom Lane <tgl> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 15 | CC: | devrim, hhorak, tgl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:fe2be58a47b5c78a5660c66f9cdeeff16f581617 | ||
Fixed In Version: | postgresql-9.0.4-3.fc15 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-06-24 03:55:15 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: |
Description
Trever Adams
2011-06-09 21:29:36 UTC
This looks like fallout from database corruption :-( Some detective work on an apparently unrelated upstream bug report has just verified that there's a bug in gcc 4.6.0 that breaks some logic in Postgres' crash recovery code. It's still not clear to me what caused your original crash (and in particular, whether or not it had anything to do with IPv6), but the follow-on crashes are very likely due to this. I am building 9.0.4-3 with a workaround right now, and I urgently recommend an upgrade as soon as it hits -testing. postgresql-9.0.4-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/postgresql-9.0.4-3.fc15 I think I found out what caused it. This is on a virtual machine. While trying to get the VM an IPv6 address per someone's instructions on the devel list, (Virsh net-destroy, virsh net-create -- don't do this while the VM is live..), things went very south once or twice. I think it did so during a write, causing the corruption. The database became so corrupted this morning, I couldn't even start Postgres. I had to blow the entire installation (/var/lib/pgsql/data) away and start over. This is fine since it is simply a short term annoyance as dspam was the only use for it. Thank you for tracking this down and fixing it. Package postgresql-9.0.4-3.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing postgresql-9.0.4-3.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/postgresql-9.0.4-3.fc15 then log in and leave karma (feedback). As I had to recreate the database, I cannot test the exact problem. However, I have four machines that make heavy use of it (I now have a Zabbix installation using it). None of them seem to be having any problems now. Thank you. postgresql-9.0.4-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 712237 has been marked as a duplicate of this bug. *** |