https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2019-08-07T21:07:26ZCeph CephFS - Bug #41034: cephfs-journal-tool: NetHandler create_socket couldn't create socket https://tracker.ceph.com/issues/41034?journal_id=1425962019-08-07T21:07:26ZNeha Ojhanojha@redhat.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Need More Info</i></li></ul><p>Can you please elaborate on this, which journal tool are you talking about? <br />If possible, could you provide steps to reproduce this issue.</p> CephFS - Bug #41034: cephfs-journal-tool: NetHandler create_socket couldn't create socket https://tracker.ceph.com/issues/41034?journal_id=1426042019-08-08T04:55:29ZAnonymous
<ul></ul><p>the cephfs-journal-tool but I also see this with the cephfs-data-scan<br />but I made a mistake, its Ubuntu 16.04, on the 18.04 I don't see it so I assume this is somehow related to either/and the Ubuntu version and its deps , or because the new mons have 2 different port and protocols and 1 causes that error</p>
<p>happy to help more if you can let me know how to provide more detail, strace maybe?</p> CephFS - Bug #41034: cephfs-journal-tool: NetHandler create_socket couldn't create socket https://tracker.ceph.com/issues/41034?journal_id=1426052019-08-08T04:56:20ZAnonymous
<ul></ul><p>I forgot to say: the tool functions work, the warning/error doesn't affect its functionality but its confusing if you don't know that</p> CephFS - Bug #41034: cephfs-journal-tool: NetHandler create_socket couldn't create socket https://tracker.ceph.com/issues/41034?journal_id=1651642020-05-07T11:46:39ZZheng Yanukernel@gmail.com
<ul><li><strong>Status</strong> changed from <i>Need More Info</i> to <i>Fix Under Review</i></li><li><strong>Pull request ID</strong> set to <i>34942</i></li></ul> CephFS - Bug #41034: cephfs-journal-tool: NetHandler create_socket couldn't create socket https://tracker.ceph.com/issues/41034?journal_id=1662542020-05-20T17:59:33ZPatrick Donnellypdonnell@redhat.com
<ul><li><strong>Project</strong> changed from <i>RADOS</i> to <i>CephFS</i></li><li><strong>Subject</strong> changed from <i>journal tool NetHandler create_socket couldn't create socket </i> to <i>cephfs-journal-tool: NetHandler create_socket couldn't create socket </i></li><li><strong>Assignee</strong> set to <i>Zheng Yan</i></li><li><strong>Target version</strong> changed from <i>v14.2.2</i> to <i>v16.0.0</i></li><li><strong>Source</strong> set to <i>Community (user)</i></li><li><strong>Backport</strong> set to <i>octopus,nautilus</i></li><li><strong>Component(FS)</strong> <i>tools</i> added</li></ul> CephFS - Bug #41034: cephfs-journal-tool: NetHandler create_socket couldn't create socket https://tracker.ceph.com/issues/41034?journal_id=1672622020-06-03T00:41:44ZPatrick Donnellypdonnell@redhat.com
<ul><li><strong>Status</strong> changed from <i>Fix Under Review</i> to <i>Pending Backport</i></li></ul> CephFS - Bug #41034: cephfs-journal-tool: NetHandler create_socket couldn't create socket https://tracker.ceph.com/issues/41034?journal_id=1673402020-06-03T12:23:20ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-4 priority-default closed" href="/issues/45853">Backport #45853</a>: octopus: cephfs-journal-tool: NetHandler create_socket couldn't create socket </i> added</li></ul> CephFS - Bug #41034: cephfs-journal-tool: NetHandler create_socket couldn't create socket https://tracker.ceph.com/issues/41034?journal_id=1673422020-06-03T12:23:27ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-4 priority-default closed" href="/issues/45854">Backport #45854</a>: nautilus: cephfs-journal-tool: NetHandler create_socket couldn't create socket </i> added</li></ul> CephFS - Bug #41034: cephfs-journal-tool: NetHandler create_socket couldn't create socket https://tracker.ceph.com/issues/41034?journal_id=1952212021-05-14T16:44:00ZLoïc Dacharyloic@dachary.org
<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>