[Swift-devel] Re: Coaster problems with proxy and gsi explained

[Mihael Hategan]

On Tue, 2010-07-13 at 00:23 -0500, wilde at mcs.anl.gov wrote:
> For whatever reason, here are the issues:
> 
> - mcs is running Ubuntu 10.x on these machines, and seems to no longer include any Sun Javas in its .soft options. So I needed to bring in my own Java.
> 
> - mcs doesnt have Globus or OSG packages, so I needed to bring in my own CA cert dir
> 
> - the login shell, by default doesnt process .bashrc; the call to .bashrc needs to go in your .profile or similar, and was missing from mine.
> 
> - after much reading up on bash startup, and fiddling, I concluded that when swift launches coasters with the ssh provider, only the .bashrc runs, not the profile, so one needs to essentially force the .profile to run in this case, or else set PATH and X509_CERT_DIR from .profile. What I did is have .bashrc call .profile if it was not previously run.

Or put those env vars in sites.xml.

In a sense, I would probably recommend that. It seems to be the only
"portable" way.

> 
> - if either .profile or .bashrc sends anything to stdout, you get this cryptic, mysterious message from swift:
> ---
> stomp$ swift -tc.file tc -sites.file crush.xml cat.swift
> Swift svn swift-r3430 cog-r2798
> 
> RunID: 20100713-0010-d3r5x92f
> Progress:
> Exception in thread "sftp subsystem 1" java.lang.OutOfMemoryError: Java heap space
> 	at com.sshtools.j2ssh.subsystem.SubsystemClient.run(SubsystemClient.java:198)
> 	at java.lang.Thread.run(Unknown Source)

That is funny. In other words a bug. Is there any easy way to reproduce
that?

> 
> ---
> Hence, dont do that :)

But I wanna!