Hide Forgot
I was building a package on RHEL6.2 snapshot 3. (python-sqlalchemy from Fedora 15) and it through a python exception for expected reasons. abrt catches and displays this exception ok. However the first time the exception was caught the VM completely locked up and unfortunately I was unable to get any state from it. After restarting it I noticed the abrt messages in the logs. I've attached those logs and the abrt directory associated with the crash. A wild guess is that abrt tried to copy something to its crash dir that caused the machine to lockup. The VM was hosted on Fedora 15.
Created attachment 533308 [details] abrt messages from /var/log/messages
Created attachment 533309 [details] The abrt crash dir associated with this lockup The particular crash details are unimportant, and I know why it happened. I'm including the abrt crash dir mainly as general info on the system
Since RHEL 6.2 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Can you please send me /etc/abrt/* and /etc/libreport/* (if you still have that machine..)
Created attachment 546290 [details] requested config
Created attachment 585214 [details] Proposed patch
Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.