Bug 413751

Summary: segfault when starting rhmd if no write permission for db files
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-cppAssignee: Gordon Sim <gsim>
Status: CLOSED CURRENTRELEASE QA Contact: Kim van der Riet <kim.vdriet>
Severity: urgent Docs Contact:
Priority: urgent    
Version: beta   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: qpidd-0.2-24.el5, qpidc-0.2-24.el5, and rhm-0.2-18.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-29 16:46:48 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 Gordon Sim 2007-12-06 11:10:26 UTC 
To reproduce:

simple case: 
    start broker as root, using default location for storage (/var/rhm)
    shutdown, change to a 'normal' user and try to restart; get segfault

or:
    create a directory for use as store location, start the broker then shutdown
    chmod -w for all the files in <store-location>/rhm/dat/
    try and restart; get segfault
Comment 1 Gordon Sim 2007-12-06 13:11:38 UTC 
Caused by aborting a transaction (around recovery) that wasn't actually started.
Fixed in rev 1432 of the rhmessaging repo.
Comment 2 Gordon Sim 2007-12-07 14:44:05 UTC 
Fixed in build.330 on qpid-test, build.41 on qpid-test4.
Comment 3 Mike Bonnet 2008-02-29 16:46:48 UTC 
Fixed in qpidd-0.2-24.el5, qpidc-0.2-24.el5, and rhm-0.2-18.el5