Failed to Start an RGW

**Table 1** Basic information
Item	Information
Source of the Problem	Online maintenance
Product	Kunpeng BoostKit
Sub-item	SDS
Service Scenario	Software/Hardware environment configuration
Component	Other
Output Time	2019-10-28
Author	Chen Xiaobo 00416232
Team	Kunpeng BoostKit
Review Result	Review passed
Review Date	2019-11-05
Release Date	2020-03-20
Keywords	Failed to start an RGW

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

The process fails to be started due to port conflicts.

Check for RGW processes.
```
ps -ef | grep rgw
```
Only one RGW process exists.
Check for RGW services in the system.
```
ll /var/lib/ceph/radosgw/
```
Eight RGW services exist.
Manually start ceph-rgw.rgw* and ceph-rgw.ceph-zip3.
```
ps -ef | grep rgw
```
rgw.ceph-zip3 is not started.
Check the corresponding RGW ports.
```
netstat -antup | grep radosgw
```
Port 7482 is not started, and port 7480 is started.
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.

Restart RGW processes.

Stop the RGW2 process.

systemctl stop ceph-radosgw@rgw.rgw2.service

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