Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The ssh session will keep running in the terminal, listening on local ports 4141 and 3142 and printing various log messages as it forwards your ecflow network traffic to the Centre.

To access HPC job output via the log server, you need to create a tunnel access for this as well. Here we use 'logserver' as an example (replace this with your qn actual logserver).

Code Block
ssh -J user1@shell.ecmwf.int user1@machine1 -C -N -L 4141:machine1:4141 -L 3142:machine2:3142 -L 9316:logserver:9316

Configure your ecflow_ui

Next, configure the connection settings for the two ecflow servers in your ecflow_ui. Make sure you Your local ecflow_ui cannot directly access ecflow servers running at the Centre. Instead, you will connect ecflow_ui to the local SSH tunnel entrance. Open ecflow_ui connection settings and make sure to use "localhost" in the "Host" fields, not the actual ECMWF hostnames. 

...

Your local ecflow_ui cannot directly access logservers running at the centreCentre. In Section 2.1.1 we have created a tunnel for logserver traffic. In order to send the the log requests from the local ecflow_ui to the local tunnel entrance, you need to add "127.0.0.1 logserver" alias in /etc/hosts on your laptop (replace "logserver" with an actual ECMWF logserver name).

...