[ceph-users] Re: Can't join new mon - lossy channel, failing

Hi, I'm running ceph version 15.2.16 (a6b69e817d6c9e6f02d0a7ac3043ba9cdbda1bdf) octopus (stable), that would mean I am not running the fix. Glad to know that an upgrade will solve the issue! Med vänliga hälsningar Josef Johansson On 8/16/23 12:05, Konstantin Shalygin wrote: Hi, On 16

[ceph-users] Re: Can't join new mon - lossy channel, failing

Hi, Let's do some serious necromancy here. I just had this exact problem. Turns out that after rebooting all nodes (one at the time of course), the monitor could join perfectly. Why? You tell me. We did not see any traces of the ip address in any dumps that we could get a hold of. I

[ceph-users] Re: Can't join new mon - lossy channel, failing

> On 16 Aug 2023, at 13:23, Josef Johansson wrote: > > I'm running ceph version 15.2.16 (a6b69e817d6c9e6f02d0a7ac3043ba9cdbda1bdf) > octopus (stable), that would mean I am not running the fix. > > Glad to know that an upgrade will solve the issue! I'm not 100% sure that this tracker,

[ceph-users] Re: Can't join new mon - lossy channel, failing

Hi, > On 16 Aug 2023, at 11:30, Josef Johansson wrote: > > Let's do some serious necromancy here. > > I just had this exact problem. Turns out that after rebooting all nodes (one > at the time of course), the monitor could join perfectly. > > Why? You tell me. We did not see any traces of

[ceph-users] Re: Can't join new mon - lossy channel, failing

As last resort we've change ipaddr of this host, and mon successfully joined to quorum. When revert ipaddr back - mon can't join, we think there something on switch side or on old mon's side. From old mon's I was checked new mon process connectivity via telnet - all works It's good to make a

[ceph-users] Re: Can't join new mon - lossy channel, failing

On 10/4/21 15:58, Konstantin Shalygin wrote: On 4 Oct 2021, at 16:38, Stefan Kooman > wrote: What procedure are you following to add the mon? # ceph mon dump epoch 10 fsid 677f4be1-cd98-496d-8b50-1f99df0df670 last_changed 2021-09-11 10:04:23.890922 created 2018-05-18

[ceph-users] Re: Can't join new mon - lossy channel, failing

On 10/4/21 15:27, Konstantin Shalygin wrote: Hi, I was make a mkfs for new mon, but mon stuck on probing. On debug I see: fault on lossy channel, failing. This is a bad (lossy) network (crc mismatch)? What procedure are you following to add the mon? Is this physical hardware? Or a (cloned)

[ceph-users] Re: Can't join new mon - lossy channel, failing

This cluster isn't use cephx. ceph.conf global settings disable it k Sent from my iPhone > On 4 Oct 2021, at 17:46, Stefan Kooman wrote: > > I'm missing the part where keyring is downloaded and used: > > ceph auth get mon. -o /tmp/keyring > ceph mon getmap -o /tmp/monmap > chown -R

[ceph-users] Re: Can't join new mon - lossy channel, failing

After this I see only logs to stderr, what exactly I should looking for? Some grep keyword? k Sent from my iPhone > On 4 Oct 2021, at 17:37, Vladimir Bashkirtsev > wrote: >  > I guess: > > strace ceph-mon -d --id mon2 --setuser ceph --setgroup ceph > > should do. > > > > Try -f

[ceph-users] Re: Can't join new mon - lossy channel, failing

I guess: strace ceph-mon -d --id mon2 --setuser ceph --setgroup ceph should do. Try -f instead of -d if you are overwhelmed with output to get mon debug output to log file. Regards, Vladimir On 5/10/21 01:27, Konstantin Shalygin wrote: On 4 Oct 2021, at 17:07, Vladimir Bashkirtsev

[ceph-users] Re: Can't join new mon - lossy channel, failing

> On 4 Oct 2021, at 17:07, Vladimir Bashkirtsev > wrote: > > This line bothers me: > > [v2:10.40.0.81:6898/2507925,v1:10.40.0.81:6899/2507925] conn(0x560287e4 > 0x560287e56000 crc :-1 s=READY pgs=16872 cs=0 l=1 rev1=1 rx=0 > tx=0).handle_read_frame_preamble_main read frame preamble

[ceph-users] Re: Can't join new mon - lossy channel, failing

This line bothers me: [v2:10.40.0.81:6898/2507925,v1:10.40.0.81:6899/2507925] conn(0x560287e4 0x560287e56000 crc :-1 s=READY pgs=16872 cs=0 l=1 rev1=1 rx=0 tx=0).handle_read_frame_preamble_main read frame preamble failed r=-1 ((1) Operation not permitted) May be it is good idea to run mon

[ceph-users] Re: Can't join new mon - lossy channel, failing

> On 4 Oct 2021, at 16:38, Stefan Kooman wrote: > > What procedure are you following to add the mon? # ceph mon dump epoch 10 fsid 677f4be1-cd98-496d-8b50-1f99df0df670 last_changed 2021-09-11 10:04:23.890922 created 2018-05-18 20:43:43.260897 min_mon_release 14 (nautilus) 0: