https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2019-03-01T11:50:42ZCeph Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1303762019-03-01T11:50:42ZRicardo Diasrdias@suse.com
<ul></ul><p>There's a strange behavior in the log just before the segfault.</p>
<p>The peer that is trying to connect to this MDS is always sending a bad `protocotol_version`:</p>
<pre>
019-02-28 17:23:11.836 7f20057a8700 10 --1- [v2:172.21.15.200:6826/1397651624,v1:172.21.15.200:6827/1397651624] >> v1:172.21.15.13:0/3427847655 conn(0x557747a95000 0x557746bf4100 :6827 s=ACCEPTING_WAIT_CONNECT_MSG_AUTH pgs=0 cs=0 l=1).handle_connect_message_2 accept of host_type 0, policy.lossy=1 policy.server=0 policy.standby=0 policy.resetcheck=0 features 0x800000000
2019-02-28 17:23:11.836 7f20057a8700 10 --1- [v2:172.21.15.200:6826/1397651624,v1:172.21.15.200:6827/1397651624] >> v1:172.21.15.13:0/3427847655 conn(0x557747a95000 0x557746bf4100 :6827 s=ACCEPTING_WAIT_CONNECT_MSG_AUTH pgs=0 cs=0 l=1).handle_connect_message_2 accept my proto 32, their proto 0
## next reply from peer
2019-02-28 17:23:11.836 7f20057a8700 10 --1- [v2:172.21.15.200:6826/1397651624,v1:172.21.15.200:6827/1397651624] >> v1:172.21.15.13:0/3427847655 conn(0x557747a95000 0x557746bf4100 :6827 s=ACCEPTING_WAIT_CONNECT_MSG_AUTH pgs=0 cs=0 l=1).handle_connect_message_2 accept my proto 32, their proto 33554433
## next reply from peer
2019-02-28 17:23:11.836 7f20057a8700 10 --1- [v2:172.21.15.200:6826/1397651624,v1:172.21.15.200:6827/1397651624] >> v1:172.21.15.13:0/3427847655 conn(0x557747a95000 0x557746bf4100 :6827 s=ACCEPTING_WAIT_CONNECT_MSG_AUTH pgs=0 cs=0 l=1).handle_connect_message_2 accept my proto 32, their proto 0
</pre>
<p>I tried to check the log of the peer (v1:172.21.15.13:0/3427847655) but the logs directory of that machine was empty.</p> Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1305322019-03-02T05:01:16ZPatrick Donnellypdonnell@redhat.com
<ul></ul><p>Same job failed in another run, so it looks reproducible: /ceph/teuthology-archive/pdonnell-2019-03-01_18:13:24-multimds-wip-pdonnell-testing-20190301.150213-distro-basic-smithi/3654808/teuthology.log</p> Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1308152019-03-06T23:30:41ZSage Weilsage@newdream.net
<ul><li><strong>Project</strong> changed from <i>Ceph</i> to <i>RADOS</i></li><li><strong>Category</strong> deleted (<del><i>msgr</i></del>)</li></ul> Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1308172019-03-06T23:41:58ZSage Weilsage@newdream.net
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>i think this will fix it, but we need to be able to reproduce first to test...</p>
<p><a class="external" href="https://github.com/ceph/ceph/pull/26803">https://github.com/ceph/ceph/pull/26803</a></p> Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1308182019-03-06T23:44:17ZSage Weilsage@newdream.net
<ul></ul><p>trying to reproduce: <a class="external" href="http://pulpito.ceph.com/sage-38524-a/">http://pulpito.ceph.com/sage-38524-a/</a></p> Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1309082019-03-07T22:59:33ZSage Weilsage@newdream.net
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Pending Backport</i></li><li><strong>Backport</strong> set to <i>luminous,mimic</i></li></ul> Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1311452019-03-08T14:46:34ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-6 priority-4 priority-default closed" href="/issues/38644">Backport #38644</a>: luminous: AsyncConnection: segmentation fault</i> added</li></ul> Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1311472019-03-08T14:46:42ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-6 priority-4 priority-default closed" href="/issues/38645">Backport #38645</a>: mimic: AsyncConnection: segmentation fault</i> added</li></ul> Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1318642019-03-12T23:18:52ZGreg Farnumgfarnum@redhat.com
<ul><li><strong>Project</strong> changed from <i>RADOS</i> to <i>Messengers</i></li></ul> Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1318832019-03-12T23:26:02ZGreg Farnumgfarnum@redhat.com
<ul><li><strong>Category</strong> set to <i>AsyncMessenger</i></li></ul> Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1454952019-09-06T22:29:21ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Pull request ID</strong> set to <i>26803</i></li></ul> Messengers - Bug #38524: AsyncConnection: segmentation faulthttps://tracker.ceph.com/issues/38524?journal_id=1837502021-01-27T20:08:30ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Status</strong> changed from <i>Pending Backport</i> to <i>Resolved</i></li></ul><p>While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".</p>