<div dir="ltr">Yadu,<div><br></div><div style>netcat/nc has been helpful in the past resolving network/port connectivity issues. I tried to write to midway port 50000 from beagle which worked:</div><div style><br></div><div style>
on midway:</div><div style><br></div><div style>$ nc -l 50000</div><div style><br></div><div style>on beagle:</div><div style><br></div><div style><div>$ netcat 128.135.112.71 50000</div><div>hello from beagle</div><div><br>
</div><div style>Gives on midway:</div><div style><div>$ nc -l 50000</div><div>hello from beagle</div><div><br></div><div style>Hope this helps with debugging.</div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, Mar 21, 2013 at 12:31 PM, Yadu Nand <span dir="ltr"><<a href="mailto:yadudoc1729@gmail.com" target="_blank">yadudoc1729@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
@Ketan, I believe I spoke too early yesterday about /lustre/beagle/yadunand folder.<div>The error, No such file or directory went away after yadunand/swiftwork directory was</div><div>created manually.</div><div>@Mihael, I think it would really help if the directory creation could be handled by swift.</div>
<div><br></div><div>Yesterday, I tried some things David asked me to try setting the following :</div><div><div>GLOBUS_HOSTNAME=<a href="tel:128.135.112.73" value="+12813511273" target="_blank">128.135.112.73</a></div><div>
GLOBUS_TCP_PORT_RANGE=50000,51000</div><div>The issue here as I understood it, is that, the workers on beagle try to connect back</div>
<div>to midway to access the files, and the IP resolves to internal IP which it can't access.</div><div>This is happening despite setting the GLOBUS_HOSTNAME explicitly. Even the port</div><div>range that I've set does not seem to be used:</div>
<div><br></div><div>Failed to start channel GSSCChannel-https://192.5.86.107:60851(2)[<a href="https://192.5.86.107:60851" target="_blank">https://192.5.86.107:60851</a>]</div><div><br></div><div>I'm also attaching a log from the beagle run.</div>
<div>The files used for the run are on midway /home/yadunand/swiftdemo-trunk/test.beagle</div><div><br></div><div>-Yadu</div><div class="im"><br><div class="gmail_quote">On Thu, Mar 21, 2013 at 2:29 AM, Mihael Hategan <span dir="ltr"><<a href="mailto:hategan@mcs.anl.gov" target="_blank">hategan@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Wed, 2013-03-20 at 15:05 -0500, Michael Wilde wrote:<br>
> Yadu, I dont think the beagle test requires you to have any directories on beagle.<br>
<br>
</div>We do the SWIFT_USERHOME thing on beagle, and that requires the modified<br>
user home to exist I think.<br>
<br>
Might be possible to attempt to create that directory automatically.<br>
<span><font color="#888888"><br>
Mihael<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Yadu Nand B
</font></span></div>
<br>_______________________________________________<br>
Swift-devel mailing list<br>
<a href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a><br>
<a href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel" target="_blank">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><font face="'courier new', monospace">Ketan</font><br><br>
</div>