Bug #6694
closedradosgw upstart script doesn't provide the -n parameter
0%
Description
I'm using the Ceph Chef Cookbook to create and manage the configuration of a new Ceph 0.67.4 cluster on Ubuntu 12.10, and the radosgw component seems to be having issues. The Upstart script itself seems to run, but the daemon stops immediately. Running the daemon manually shows that it can't find a keyring to use to authenticate with the cluster.
It seems that the radosgw daemon uses a default name different than the Chef configuration sets up. My hostname is swift1, and Chef creates a configuration block in /etc/ceph/ceph.conf called client.radosgw.swift1 and generates a keyring named ceph.client.radosgw.swift1.keyring. However, the radosgw seems to not find its keyring unless I explicitly add -n client.radosgw.swift1. Adding this -n parameter to the initctl line of /etc/init/radosgw-all-starter.conf seems to make it start right up.
I've attached the daemon startup output with the following commands:
radosgw cluster=ceph id=radosgw.swift1 -d --debug_ms=9 -c /etc/ceph/ceph.conf > /tmp/radosgw-without-name.log
radosgw cluster=ceph id=radosgw.swift1 -n client.radosgw.swift1 -d --debug_ms=9 -c /etc/ceph/ceph.conf > /tmp/radosgw-with-name.log
Is there a different way to set the name? Should ceph.conf have the radosgw settings in a different section?
Files