Opened 3 years ago

Closed 3 years ago

#2179 closed help (fixed)

Submitting problem from PUMA

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

Description

I encountered a problem of submitting the suite job with rose. Attached is the error information. It seems that the problem is the connection from PUMA to ARCHER. However, I could login to ARCHER from PUMA without entering the password. Following the UM training course, I tried to reset up an ssh connection from PUMA to ARCHER:

  1. Run ‘~um/um-training/install-ssh-keys jfgu@…’. After entering the passphrase, there is no request for ARCHER password;
  2. When I login in to ARCHER, I didn’t get asked for passphrase, either. The training said this indicates something has gone wrong. I open the file ~/.ssh/authorized_keys, just the first few words are the same as that in the training material. Here it is:


ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC0lLh5MtONT/mCGKWcqNVx61h9K0jHwY8ZZD4ApdiKTtQAFyXuJlqS4FhKXH04Q1yPBzmBzuHIW6HlS7G1L4+Dh0l/DGW10k40swOiELYauanDMejN9Yuorn4kGYRd2dyKIBoOyBvA66kF81cgByo7FkK74Aw+zeXzWjVFPm/FKH6zUBjkzb5brMnjJbpG5BPxjQ2MuO/t4lPqfug+/ZX/deFztw7+26hOg7ig112DO0jHDnIPIE1oRQVkO4ItVyd8obqdc8+uLQyT3ORvItjmmqPNSuxPPjKQw29wFHjYOagZ+4P4YxmspD8sEFw4WaqjjD998irJyQTeeGCPAZGt jfgu@puma
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDCM1WdoCy8FBLhl4H8LccOQD3IYVMwqDjyFZVtzvdJW9yWa7zI/X6WrzCWJimh8VB8/ajuYQEgPLB4mp+h7VQDJDkR6RwbQmkvSQe/M/467/WNn1DA8LhcCd9kWYLCPi1v/dYUyOnQCVpZH/a2v9MEt2XYvG00AVqQHhQkbbgC518BC7BvGvmpUqnnlvf4GeBM0hnigJa6ksu/WohORwTmdVf2XkbKEjYD7oKV9EBgmmLZhcksYSzVPuuIhXbEmH5p6amSi28ojTbKetI/9O3MPkBgJD5yymxA8ObAVRykA7Hef+tRHEgJpHJwKa+HMtRG5z5Ynn8HMV9fpYVWFEaL jfgu@puma

Attachments (1)

submit problem.png (428.6 KB) - added by jfgu 3 years ago.

Download all attachments as: .zip

Change History (5)

Changed 3 years ago by jfgu

comment:1 Changed 3 years ago by jfgu

Could someone help me to fix this problem? I am a new UM user. Thank you very much!

comment:2 Changed 3 years ago by grenville

You need to set your HPC_USER (in the jinja2 screen) — the screen you attached shows the problem - it thinks you are "username_here"

Grenville

comment:3 Changed 3 years ago by jfgu

Oh, yes, I forgot that. Thank you Grenville!

comment:4 Changed 3 years ago by grenville

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