Closed solejar closed 8 years ago
Hey Sean,
Just to make sure, to interactively login from workflows to stampede/comet, you need to use gsissh stampede/comet
and not ssh. The RP examples (along with config.json) should already be doing that.
I also faced this issue. Might not be the same cause (in my case, I required a new certificate). Could you try:
$ myproxy-logon
<enter xsede password when prompted>
$ gsissh stampede
That fixed it! Not sure why it was working fine originally and then stopped working today, but the myproxy-logon
got it working.
Great !
The default proxy lifetime on the workflow machine is, I believe, 24 hours or so. If you keep your session alive longer than that, you'll end up with an invalid proxy. Or indeed, as it happened to Vivek, if you create a proxy for BlueWaters, that new proxy will overwrite (and thus invalidate) the old XSEDE proxy...
FWIW, the option -t 48
to myproxy-logon
will give you a proxy which is valid for two days. I think the max is 10 days usually.
I actually thought a new certificate is obtained every time I login, since I don't think I faced this issue before yesterday (during the previous tutorial setups, etc.). Maybe they changed it ?
Currently, default is 12 hours and max is 11 days.
Yes, its obtained every time you login. But if you keep your session alive for longer than those 12 hours, the proxy will be dead...
Ah ok, that makes sense. Thanks !
I got most of the example scripts working on Stampede yesterday without error. That was in the office on a wired connection. I am now trying to run them at home on my wireless connection and I am getting some sort of SSH permission denial. I do not know what the origin of this error is, as I thought that the workflow machine automatically allowed for passwordless SSHing into XSEDE machines. I tried SSHing manually into Stampede, and I got the same permission denial. The error occurs at the pilot submission stage.