Hi Noah, On Wed, 2014-12-10 at 11:12 -0800, Noah Watkins wrote: > > On Dec 9, 2014, at 9:26 PM, Andy Grover <agrover@xxxxxxxxxx> wrote: > > > > On 12/09/2014 04:22 PM, Noah Watkins wrote: > >> Hi, I’m trying to debug a problem setting up an iSCSI target portal > >> on aarch64. I’m seeing -EADDRINUSE when I create the portal: > > > > Hmm interesting, haven't tried on aarch64 but can't think of why it'd matter. > > Hi Andy, > > Thanks for your reply. I tried several times to reproduce this > EADDRINUSE error, but without no luck. Apparently this problem doesn’t > exist anymore :) > Btw, this type of EADDRINUSE failure can occur when one program is already listening on INADDR_ANY (0.0.0.0) on $SOME_PORT, and then another program attempts to listen on a non INADDR_ANY address (like 10.10.1.2 in your example) on $SOME_PORT. Note this is not specific to iSCSI, and Linux/Net will return the same error for any programs that attempt this. --nab -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
