Closed euhruska closed 8 years ago
RuntimeError: schema ssh unknown for resource ncsa.bw
It seems to use ssh
instead of gsissh
. I am not sure whats up. What version of RP are you using? (radicalpilot-version
)
@vivek-bala : vivek, could that be a misconfiguration on the EnMD layer?
radicalpilot-version 0.40.1
Yeah, ssh
is not supported in that version, so the message complains about the right thing at least :) We'll have to wait for Vivek to reply I'm afraid, not sure where ssh instead of gsissh is picked up...
I think you can add this to the arguments of the SingleClusterEnvironment
:
access_schema = 'gsissh'
I am not sure what exactly you run, and if that SingleClusterEnvironment
lives in your part of the code at all...
Good, might have fixed this. At least, it doesn't throw this error anymore, currently waiting in queue.
if not unspecified, schema defaults to None.
Yeah, ssh is not supported in that version, so the message complains about the right thing at least :)
I don't understand. ssh is not supported ??
Hmmm, good to know. I have tried on BW, it seems to be working unspecified. Thinking why it doesn't for you.
I don't understand. ssh is not supported ??
Have a look at https://github.com/radical-cybertools/radical.pilot/blob/devel/src/radical/pilot/configs/resource_ncsa.json#L27 -- you'll see that this RP level config only defines gsissh endpoints for bw, not plain ssh.
Ah yes yes. You meant for BW, got confused :).
If schema is set to None from EnMD, RP should default to gsissh in the case of BW. Right ? @euhruska Eugen, so it works only if you specify for access_schema to gsissh in your case ?
Yes, before the access_schema was unspecified and it didn't work. I only added that one line.
If schema is set to None from EnMD, RP should default to gsissh in the case of BW. Right ?
Yes, and that seems to work on on RP level:
schema
key in examples/config.json
to null
examples/00_getting_started.py ncsa.bw
So my assumption would be that EnMD falls back to ssh? If that is not the case, I should start looking where we go wrong. Could you print the pilot description before submission?
Hmmm, I'm not sure why it would happen though.
https://github.com/radical-cybertools/radical.ensemblemd/blob/master/src/radical/ensemblemd/single_cluster_environment.py#L228 where it is assigned to the pilot. Lines 44, 65 of interest as well.
Ah wait. @euhruska I think you might be using the released version of EnMD. Could you confirm the version please ? If so, please use the master branch.
================================================================================
EnsembleMD (0.3.14)
================================================================================
Ok, that's the released version. Please try with the master branch.
sure
How do I install the master branch with pip?
pip install --upgrade git+https://github.com/radical-cybertools/radical.ensemblemd.git@master#egg=radical.ensemblemd
I seem to have problems using radical.pilot with bluewaters. It shows an error like it can't connect. But I can connect as usual to bluewaters with
gsissh hruska@bw.ncsa.illinois.edu
. Though it says/Users/eh/Library/Globus/etc/ssh not found.
in the first line before connecting. my $GLOBUS_LOCATION is /Users/eh/Library/Globus The error message is when running radical.pilot:This worked before and I didn't change Globus toolkit, just update radical installation. What is the problem?