Skip to content

Commit 68e0d99

Browse files
authored
Merge pull request ceph#54625 from zdover23/wip-doc-2023-11-23-rados-troubleshooting-mon-client-cant-connect
doc/rados: edit "client can't connect..." Reviewed-by: Cole Mitchell <[email protected]>
2 parents 2139231 + ec29809 commit 68e0d99

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

doc/rados/troubleshooting/troubleshooting-mon.rst

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -481,12 +481,13 @@ Clock Skew Questions and Answers
481481
Client Can't Connect or Mount
482482
-----------------------------
483483

484-
Check your IP tables. Some operating-system install utilities add a ``REJECT``
485-
rule to ``iptables``. ``iptables`` rules will reject all clients other than
486-
``ssh`` that try to connect to the host. If your monitor host's IP tables have
487-
a ``REJECT`` rule in place, clients that are connecting from a separate node
488-
will fail and will raise a timeout error. Any ``iptables`` rules that reject
489-
clients trying to connect to Ceph daemons must be addressed. For example::
484+
If a client can't connect to the cluster or mount, check your iptables. Some
485+
operating-system install utilities add a ``REJECT`` rule to ``iptables``.
486+
``iptables`` rules will reject all clients other than ``ssh`` that try to
487+
connect to the host. If your monitor host's iptables have a ``REJECT`` rule in
488+
place, clients that connect from a separate node will fail, and this will raise
489+
a timeout error. Look for ``iptables`` rules that reject clients that are
490+
trying to connect to Ceph daemons. For example::
490491

491492
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited
492493

0 commit comments

Comments
 (0)