[Gluster-devel] OS X 10.5 PPC client does not connect
From:
Ate Poorthuis
Subject:
[Gluster-devel] OS X 10.5 PPC client does not connect
Date:
Thu, 2 Jul 2009 14:14:39 +0200
Hi,
Gluster clients running on PPC on Mac OS X 10.5 are not able to connect to the server. The exact same configuration on a OS X intel machine works perfectly. I have the following errors in my logs.
Client:
[2009-07-02 14:02:46] D [glusterfsd.c:256:_add_fuse_mount] glusterfs: 'direct-io-mode' in fuse causes data corruption if O_APPEND is used. disabling 'direct-io-mode' [2009-07-02 14:02:46] D [glusterfsd.c:1179:main] glusterfs: running in pid 41655
[2009-07-02 14:02:46] D [client-protocol.c:5948:init] gfs-001-afr1: defaulting frame-timeout to 30mins [2009-07-02 14:02:46] D [client-protocol.c:5956:init] gfs-001-afr1: setting ping-timeout to 5 [2009-07-02 14:02:46] D [transport.c:141:transport_load] transport: attempt to load file /usr/local/gluster/lib/glusterfs/2.0.2/transport/socket.so
[2009-07-02 14:02:46] D [transport.c:141:transport_load] transport: attempt to load file /usr/local/gluster/lib/glusterfs/2.0.2/transport/socket.so [2009-07-02 14:02:46] D [dict.c:297:dict_get] dict: @this=0x0 @key=0xf4c2c
[2009-07-02 14:02:46] D [client-protocol.c:6276:notify] gfs-001-afr1: got GF_EVENT_PARENT_UP, attempting connect on transport [2009-07-02 14:02:46] D [client-protocol.c:6276:notify] gfs-001-afr1: got GF_EVENT_PARENT_UP, attempting connect on transport
[2009-07-02 14:02:46] D [client-protocol.c:6276:notify] gfs-001-afr1: got GF_EVENT_PARENT_UP, attempting connect on transport [2009-07-02 14:02:46] D [client-protocol.c:6276:notify] gfs-001-afr1: got GF_EVENT_PARENT_UP, attempting connect on transport
[2009-07-02 14:02:46] N [glusterfsd.c:1198:main] glusterfs: Successfully started [2009-07-02 14:02:46] D [client-protocol.c:6290:notify] gfs-001-afr1: got GF_EVENT_CHILD_UP [2009-07-02 14:02:46] D [client-protocol.c:6290:notify] gfs-001-afr1: got GF_EVENT_CHILD_UP
[2009-07-02 14:02:46] E [saved-frames.c:165:saved_frames_unwind] gfs-001-afr1: forced unwinding frame type(2) op(SETVOLUME) [2009-07-02 14:02:46] D [client-protocol.c:5483:client_setvolume_cbk] gfs-001-afr1: setvolume failed (Socket is not connected)
[2009-07-02 14:02:46] E [saved-frames.c:165:saved_frames_unwind] gfs-001-afr1: forced unwinding frame type(2) op(SETVOLUME) [2009-07-02 14:02:46] D [client-protocol.c:5483:client_setvolume_cbk] gfs-001-afr1: setvolume failed (Socket is not connected)
[2009-07-02 14:02:46] D [fuse-bridge.c:2378:fuse_root_lookup_cbk] fuse: first lookup on root failed. [2009-07-02 14:02:46] D [client-protocol.c:1738:client_statfs] gfs-001-afr1: STATFS 1 (/): failed to get remote inode number
[2009-07-02 14:02:46] W [fuse-bridge.c:1837:fuse_statfs_cbk] glusterfs-fuse: 0: ERR => -1 (Socket is not connected)
Server:
[2009-07-02 14:02:46] E [socket.c:584:__socket_proto_state_machine] server: socket header validate failed (10.0.0.169:1023). possible mismatch of transport-type between server and client volumes, or version mismatch
[2009-07-02 14:02:46] N [server-protocol.c:7796:notify] server: 10.0.0.169:1023 disconnected [2009-07-02 14:02:46] E [socket.c:584:__socket_proto_state_machine] server: socket header validate failed (10.0.0.169:1022). possible mismatch of transport-type between server and client volumes, or version mismatch
[2009-07-02 14:02:46] N [server-protocol.c:7796:notify] server: 10.0.0.169:1022 disconnected [2009-07-02 14:02:46] E [socket.c:584:__socket_proto_state_machine] server: socket header validate failed (10.0.0.169:1023). possible mismatch of transport-type between server and client volumes, or version mismatch
[2009-07-02 14:02:46] N [server-protocol.c:7796:notify] server: 10.0.0.169:1023 disconnected [2009-07-02 14:02:46] E [socket.c:584:__socket_proto_state_machine] server: socket header validate failed (10.0.0.169:1023). possible mismatch of transport-type between server and client volumes, or version mismatch
[2009-07-02 14:02:46] N [server-protocol.c:7796:notify] server: 10.0.0.169:1023 disconnected