<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
what's in the client logs and the brick logs in
/var/log/glusterfs/*log and /var/log/glusterfs/bricks/*log<br>
<br>
On 2/23/12 4:49 PM, Carl Boberg wrote:
<blockquote
cite="mid:CANnFLQwZHpjrVkHCrME0wWFBUFs_ZJQv1dWVHBQRi6HSkTDQag@mail.gmail.com"
type="cite">Hello
<div><br>
</div>
<div>I have just started to prepare a smallish production setup
(nothing critical running on it yet).<br>
<div><br>
</div>
<div>I have 2 gluster servers with 8 volumes and Im getting a
lot of theese warnings in the cli.log</div>
<div>[2012-02-23 22:32:15.808271] W
[rpc-transport.c:606:rpc_transport_load] 0-rpc-transport:
missing 'option transport-type'. defaulting to "socket"</div>
<div><br>
</div>
<div>Could be related to the warinings in
the etc-glusterfs-glusterd.vol.log</div>
<div>
<div>[2012-02-21 17:28:15.279406] W
[socket.c:1494:__socket_proto_state_machine]
0-socket.management: reading from socket failed. Error
(Transport endpoint is not connected), peer (<a
moz-do-not-send="true" href="http://10.131.139.26:1019">10.131.139.26:1019</a>)</div>
<div>[2012-02-21 17:28:15.279521] W
[socket.c:1494:__socket_proto_state_machine]
0-socket.management: reading from socket failed. Error
(Transport endpoint is not connected), peer (<a
moz-do-not-send="true" href="http://10.131.139.26:1016">10.131.139.26:1016</a>)</div>
<div>[2012-02-21 17:28:19.236986] W
[socket.c:1494:__socket_proto_state_machine]
0-socket.management: reading from socket failed. Error
(Transport endpoint is not connected), peer (<a
moz-do-not-send="true" href="http://10.131.139.25:1013">10.131.139.25:1013</a>)</div>
<div>
<div>[2012-02-21 17:28:42.660021] W
[socket.c:1494:__socket_proto_state_machine]
0-socket.management: reading from socket failed. Error
(Transport endpoint is not connected), peer (<a
moz-do-not-send="true" href="http://127.0.0.1:1012">127.0.0.1:1012</a>)</div>
<div>[2012-02-21 17:34:58.405575] W
[socket.c:1494:__socket_proto_state_machine]
0-socket.management: reading from socket failed. Error
(Transport endpoint is not connected), peer (<a
moz-do-not-send="true" href="http://10.131.139.9:1021">10.131.139.9:1021</a>)</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>where 10.131.139.26 and 25 are the 2 servers
and 10.131.139.9 is a client (other clients ip:s are also
showing up)</div>
<div><br>
</div>
<div>'gluster peer status' on either server says everything is
fine and connected and im not experiencing any problems. Im
just a little nervous about the warnings since they get
logged quite often. Would be greatful for som insight in the
reason for theese warnings.</div>
<div><br>
</div>
<div>gluster 3.2.5 rpm install
</div>
<div>all clients and servers are RedHat 6.1 using native
client</div>
<div><br>
</div>
<div>Best regards</div>
---<br>
Carl Boberg<br>
Operations<br>
<br>
Memnon Networks AB<br>
Tegnérgatan 34, SE-113 59 Stockholm<br>
<br>
Mobile: +46(0)70 467 27 12<br>
<a moz-do-not-send="true" href="http://www.memnonnetworks.com"
target="_blank">www.memnonnetworks.com</a><br>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://gluster.org/cgi-bin/mailman/listinfo/gluster-users">http://gluster.org/cgi-bin/mailman/listinfo/gluster-users</a>
</pre>
</blockquote>
</body>
</html>