Project

General

Profile

Actions
Copy link

Bug #8111

closed

/etc/init.d/ceph-radosgw for RHEL needs QA

Added by John Wilkins about 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

During testing of the insallation procedure for RHEL, I found it possible to start ceph-radosgw in user space, but I could not get it started with sysvinit at /etc/init.d/ceph-radosgw start. The script needs to be verified to run on RHEL, and the various permissions/ownership for /var/run/ceph, /var/log/ceph, etc. need to be clearly identified so that the installation and configuration procedure can be accurately documented for ceph-radosgw with RHEL.

Actions
Copy link
 #1

Updated by Ian Colle about 10 years ago

  • Assignee set to Yehuda Sadeh
Actions
Copy link
 #2

Updated by Sage Weil almost 10 years ago

  • Project changed from Ceph to rgw
  • Category deleted (22)
Actions
Copy link
 #3

Updated by Sage Weil over 9 years ago

  • Status changed from New to Need More Info
  • Assignee deleted (Yehuda Sadeh)
  • Source changed from other to Development

isn't it /etc/init.d/radosgw?

Actions
Copy link
 #4

Updated by John Wilkins over 9 years ago

  • Status changed from Need More Info to Resolved

I believe this issue cropped up because of using other than short host name. Ran through this with Tamil, and the note here: http://ceph.com/docs/master/radosgw/config/#add-a-gateway-configuration-to-ceph resovled the issue. Not using the FQDN, or alternatively a name clash for asok files prevents the daemon from starting.

Actions
Copy link

Also available in: Atom PDF