Hi 胡 玮文,
On 10.01.22 19:27, 胡 玮文 wrote:
So this cluster is deployed with cephadm. Please use
systemctl status ceph-b61400fe-6e25-11ec-b322-896f8c260566@mon.mon01.service
OK, this gives another picture:
root@mon01:~# systemctl status
> 在 2022年1月11日，00:19，Andre Tann 写道：
>
> Hi Janne,
>
>> On 10.01.22 16:49, Janne Johansson wrote:
>>
>> Well, nc would not tell you if a bad (local or remote) firewall
>> configuration prevented nc (and ceph -s) from connecting, it would
>> give the same results as if the daemon wasn't
Hi Janne,
On 10.01.22 16:49, Janne Johansson wrote:
Well, nc would not tell you if a bad (local or remote) firewall
configuration prevented nc (and ceph -s) from connecting, it would
give the same results as if the daemon wasn't listening at all, so
that is why I suggested checking if the port
Den mån 10 jan. 2022 kl 16:24 skrev Andre Tann :
> Hi Janne,
> On 10.01.22 16:13, Janne Johansson wrote:
> > modern clusters use msgr2 communications on port 3300 by default I think.
> > Also, check on the 192.168.14.48 host with "netstat -an | grep LIST"
> > or "ss -ntlp" if something is
Hi Janne,
On 10.01.22 16:13, Janne Johansson wrote:
modern clusters use msgr2 communications on port 3300 by default I think.
Also, check on the 192.168.14.48 host with "netstat -an | grep LIST"
or "ss -ntlp" if something is listening on 6789 and/or 3300.
Yes, I already checked 3300 and
I would go with the ss tool, because netstat shortens IPv6 addresses, so
you don't see if it is actually listening on the correct address.
Am Mo., 10. Jan. 2022 um 16:14 Uhr schrieb Janne Johansson <
icepic...@gmail.com>:
> modern clusters use msgr2 communications on port 3300 by default I
modern clusters use msgr2 communications on port 3300 by default I think.
Also, check on the 192.168.14.48 host with "netstat -an | grep LIST"
or "ss -ntlp" if something is listening on 6789 and/or 3300.
Den mån 10 jan. 2022 kl 16:10 skrev Andreas Feile :
>
> Hi all,
>
> I've set up a 6-node ceph
