Failed to Start an RGW

Symptom

An RGW fails to be started due to RGW port conflicts.

Key Process and Cause Analysis

The process fails to be started due to port conflicts.

Conclusion and Solution

1. Check for RGW processes.

   ps -ef | grep rgw

   Only one RGW process exists.

   

2. Check for RGW services in the system.

   ll /var/lib/ceph/radosgw/

   

   Eight RGW services exist.

3. Manually start ceph-rgw.rgw* and ceph-rgw.ceph-zip3.

   ps -ef | grep rgw

   

   rgw.ceph-zip3 is not started.

4. Check the corresponding RGW ports.

   netstat -antup | grep radosgw

   

   Port 7482 is not started, and port 7480 is started.

5. Check for the configuration file. In the configuration file, port 7480 corresponds to the ceph-zip* RGW process, and port 7482 corresponds to the RGW2 process. It can be inferred that the process startup failure is caused by a port conflict.

   

6. Restart RGW processes.
   1. Stop the RGW2 process.

      systemctl stop ceph-radosgw@rgw.rgw2.service

   2. Start the ceph-zip3 and RGW2 processes. The problem is solved.

      systemctl start ceph-radosgw@rgw.ceph-zip3.service
      systemctl start ceph-radosgw@rgw.rgw2.service