Den mån 10 jan. 2022 kl 16:24 skrev Andre Tann <atann@xxxxxxxxxxxx>: > 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 6789, and these are closed: 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 was listening or not, instead of doing a wide test that may have multiple causes for same failure. > >> root@mon01:~# nc -z 192.168.14.48 6789; echo $? > >> 1 > >> root@mon01:~# nc -z 192.168.14.48 3300; echo $? > >> 1 > > Doublechecking if someone is listening there: > > root@mon01:~# ss -ntlp | egrep '(3300|6789)' > root@mon01:~# > > I'm on the right host: > root@mon01:~# ip a | grep '192.168.14.48' > inet 192.168.14.48/24 brd 192.168.14.255 scope [...] > > So indeed no process listening on one of these ports. so if 192.168.14.48 indeed is a mon host, then "systemctl" should show if the ceph-mon@<my-hostname> is running or not, and logs from /var/log/ceph/ceph-mon-hostname.log should indicate why it will not start or why it is not running currently. -- May the most significant bit of your life be positive. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |