Bug #41034
closedcephfs-journal-tool: NetHandler create_socket couldn't create socket
0%
Description
Ubuntu 18.04 with ceph Nautilus repo
Journal tool is broken:
2019-07-31 19:36:56.879 7f57bf308700 -1 NetHandler create_socket couldn't create socket (97) Address family not supported by protocol
Updated by Neha Ojha over 4 years ago
- Status changed from New to Need More Info
Can you please elaborate on this, which journal tool are you talking about?
If possible, could you provide steps to reproduce this issue.
Updated by Anonymous over 4 years ago
the cephfs-journal-tool but I also see this with the cephfs-data-scan
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
happy to help more if you can let me know how to provide more detail, strace maybe?
Updated by Anonymous over 4 years ago
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
Updated by Zheng Yan almost 4 years ago
- Status changed from Need More Info to Fix Under Review
- Pull request ID set to 34942
Updated by Patrick Donnelly almost 4 years ago
- Project changed from RADOS to CephFS
- Subject changed from journal tool NetHandler create_socket couldn't create socket to cephfs-journal-tool: NetHandler create_socket couldn't create socket
- Assignee set to Zheng Yan
- Target version changed from v14.2.2 to v16.0.0
- Source set to Community (user)
- Backport set to octopus,nautilus
- Component(FS) tools added
Updated by Patrick Donnelly almost 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #45853: octopus: cephfs-journal-tool: NetHandler create_socket couldn't create socket added
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #45854: nautilus: cephfs-journal-tool: NetHandler create_socket couldn't create socket added
Updated by Loïc Dachary almost 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".