Re: connection attempt on 127.0.0.1:24007 failed ?

Joe Julian <joe@xxxxxxxxxxxxxxxx> · Fri, 17 Feb 2017 08:23:30 -0800

"invalid argument" in socket could be:

EINVAL Unknown protocol, or protocol family not available. 

EINVAL Invalid flags in type

Since we know that the flags don't cause errors elsewhere and don't change from one installation to another I think it's safe to disregard that possibility.

That leaves the former. Obviously TCP is a known protocol. That leaves "protocol family not available". I haven't read the kernel code for this but of the top of my head I would look for ipv4 (if you are ipv6 only that's an invalid address) or socket exhaustion.

On February 17, 2017 7:47:23 AM PST, lejeczek <peljasz@xxxxxxxxxxx> wrote:

    hi guys

    in case it's something trivial and I start digging, removing bits. I
    see these logged every couple of seconds on one peer:

    [2017-02-17 15:44:40.012078] E [socket.c:3097:socket_connect]
    0-glusterfs: connection attempt on 127.0.0.1:24007 failed, (Invalid
    argument)

    [2017-02-17 15:44:43.837139] E [socket.c:3097:socket_connect]
    0-glusterfs: connection attempt on 127.0.0.1:24007 failed, (Invalid
    argument)

    and sometimes:

    [2017-02-17 15:45:18.414234] E
    [glusterfsd-mgmt.c:1908:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed
    to connect with remote-host: localhost (Transport endpoint is not
    connected)

    [2017-02-17 15:45:18.414260] I
    [glusterfsd-mgmt.c:1926:mgmt_rpc_notify] 0-glusterfsd-mgmt:
    Exhausted all volfile servers

    I this caused by local to the peer mount requests?

    b.w.

    L.

-- 

Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users