Bug 413751 - segfault when starting rhmd if no write permission for db files
Summary: segfault when starting rhmd if no write permission for db files
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: beta
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
: ---
Assignee: Gordon Sim
QA Contact: Kim van der Riet
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-06 11:10 UTC by Gordon Sim
Modified: 2009-05-07 20:09 UTC (History)
0 users

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:
Clone Of:
Environment:
Last Closed: 2008-02-29 16:46:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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