Actions
Bug #38033
closedRGW "Caught signal (Aborted)" when running vstart with RGW option
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
RGW is not running on my local test system after executing "RGW=1 ../src/vstart.sh -n -x".
There is no error in the output of vstart, but e.g. "ceph -s" shows that RGW is not running.
Found the following in the rgw log:
-2> 2019-01-23 15:50:55.739 7f51257ea700 0 RGWReshardLock::lock failed to acquire lock on reshard.0000000001 ret=-16
-1> 2019-01-23 15:50:55.739 7f51257ea700 5 process_single_logshard(): failed to acquire lock on reshard.0000000001
0> 2019-01-23 15:50:55.739 7f5149e5ddc0 -1 *** Caught signal (Aborted) **
in thread 7f5149e5ddc0 thread_name:radosgw
ceph version 14.0.1-2864-gba556a7722 (ba556a77222f8c4f604693ea1ccc8db1bad57af7) nautilus (dev)
I attached a more detailed log output as well as the ceph.conf file.
For reference: I'm using https://github.com/ricardoasmarques/ceph-dev-docker for my Ceph dev environment (openSUSE Tumbleweed)
Files
Updated by Matt Benjamin about 5 years ago
- Status changed from New to Pending Backport
- Assignee set to Matt Benjamin
Updated by Casey Bodley about 5 years ago
- Is duplicate of Bug #24228: RGW fails to start on Fedora 28 from default configuration added
Updated by Nathan Cutler about 5 years ago
- Status changed from Pending Backport to Duplicate
Actions