Opened 5 years ago

Closed 4 years ago

#1581 closed help (answered)

JASMIN login via ARCHER cray-mpich conflict error

Reported by: Leighton_Regayre Owned by: um_support
Component: UM Model Keywords:
Cc: Platform:
UM Version: <select version>


In attempting to login to JASMIN so that I can transfer data from /work I'm given the following error:
Module 'cray-mpich/7.1.1' conflicts with the currently loaded module(s) 'cray-mpich/6.3.1'

after entering the command:
exec ssh-agent /bin/bash

I've previously had no problem logging onto JASMIN via ARCHER.



Change History (7)

comment:1 Changed 5 years ago by grenville


Was there a failure - this isn't an error message, its just for info? This message shouldn't affect logging on.


comment:2 Changed 5 years ago by Leighton_Regayre


Yes there was an error after that step.

When I enter:
ssh -AX lregayre@…

I'm given the error:
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

I've set my paired keys as CEDA require and have copied the public key to myCEDA. I've logged in previously and have gone through this process again (~30 mins ago). Is there a problem we can tackle from our end?


comment:3 Changed 5 years ago by annette


If you are having trouble logging into Jasmin then you should contact the CEDA helpdesk by emailing support@…


comment:4 Changed 5 years ago by annette

  • Resolution set to answered
  • Status changed from new to closed

comment:5 Changed 4 years ago by Leighton_Regayre

  • Resolution answered deleted
  • Status changed from closed to reopened


I have been in contact with the CEDA helpdesk over the past months and they have not been able to isolate the problem. Their jasmin experts have suggested that I login using:

ssh -o ServerAliveInterval?=300 lregayre@…

but this doesn't fix the problem. Sessions are still killed within a minute. CEDA helpdesk claim the signal is being killed from ARCHER. Has this happened to anyone previously?



comment:6 Changed 4 years ago by grenville


I should have answered this better earlier, but had forgotten ARCHER policy; ARCHER does not allow outbound ssh sessions. You can only ssh into ARCHER.


comment:7 Changed 4 years ago by grenville

  • Resolution set to answered
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.