<div dir="ltr">Hello!<div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 30, 2017 at 2:14 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
</div></div>The best logging you can get is when you use the glfs_set_logging()<br>
call:<br>
<a href="https://github.com/gluster/glusterfs/blob/release-3.12/api/src/glfs.h#L199" rel="noreferrer" target="_blank">https://github.com/gluster/<wbr>glusterfs/blob/release-3.12/<wbr>api/src/glfs.h#L199</a><br>
<br>
Make sure that the process can create the logfile. By default the<br>
log-level is set to INFO(7), setting it to DEBUG(8) or TRACE(9) might be </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">helpful.<br>
<br></blockquote><div><br></div><div>Ok, it will take some time to implement...</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The connection to glusterd is only for the management part. Once<br>
glfs_init() is called, the volume layout is fetched from glusterd, and<br>
based on those details, the connections to the bricks are made. You can<br>
check the logs from the bricks to see if connections go established.<br>
Capturing a tcpdump on the system where the gfapi application is running<br>
and loading it in wireshark can show more whats happening on the network<br>
side (wireshark knows most of the Gluster protocol).<br>
<br></blockquote><div><br></div><div>Looks like it loads volinfo and everything stops here. I attached my dump file, so you make take a look on it if you like. </div></div></div></div>