Project

General

Profile

Actions

Bug #44661

closed

radosgw can't bind to reserved port (443)

Added by Chris Durham about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Target version:
% Done:

0%

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

Description

Using ceph-radosgw from http://http://download.ceph.com/rpm-octopus/el8/x86_64/ceph-radosgw-15.1.1-0.el8.x86_64.rpm on CentOS 8.1

I have the following setup in /etc/ceph/ceph.conf for radosgw:

[client.rgw.node1]
host = node1
rgw frontends = beast ssl_endpoint=0.0.0.0 ssl_certificate=/etc/ceph/cert.pem

The gateway does not startup. I have, in the log (debug rgw = 20) the following:

2020-03-17T14:10:11.249-0400 7f96f9c4e280 -1 failed to bind address 0.0.0.0:443: Permission denied

If I change to a port > 1024, such as:

rgw frontends = beast ssl_endpoint=0.0.0.0:7480 ssl_certificate=/etc/ceph/cert.pem

That works fine.

Same error if use the local IP address in ssl_endpoint instead of 0.0.0.0. The same error occurs if I use civetweb instead

This has worked fine on earlier releases with the exact same configuration file.

No, nothing else is running on 443 :-).

selinux is ceph-selinux-15.1.1-0.el8.x86_64 from the same repo if that matters


Related issues 3 (0 open3 closed)

Related to Orchestrator - Bug #45197: cephadm: rgw: failed to bind address 0.0.0.0:80Duplicate

Actions
Related to Orchestrator - Feature #43911: test cephadm rgw deploymentResolved

Actions
Copied to rgw - Backport #45215: octopus: radosgw can't bind to reserved port (443)ResolvedNathan CutlerActions
Actions

Also available in: Atom PDF