Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: adapted to cci

Problem

Your MARS You are running mars on the ECMWF cloud, and your request is stuck, showing messages such as the followingan the last message is similar to:

No Format
mars - INFO   - 2020030220230627.105633103107 - Calling mars on '10mars.3ecmwf.165.120int', local port is 5171450801
mars - WARNINFO   - 2020030220230627.105840103107 - connectCallback : 10.3.165.120 9000 (Connection timed out)
mars - WARN   - 20200302.110052 - connect : 10.3.165.120 9000 (Connection timed out)
mars - WARN   - 20200302.110304 - connect : 10.3.165.120 9000 (Connection timed out)
mars - WARN   - 20200302.110517 - connect : 10.3.165.120 9000 (Connection timed out)
...

Solution

Your VM does not seem to have the data network enabled, so MARS cannot reach the server. At this point you have 2 options:

Provision a new VM instance

at address 192.168.1.X, port 50801

Solution

MARS client does not know your external IP address, so it only listens for the server to contact on a private (192.168.1.X) IP address which MARS servers cannot reach. This may be the case if your VM is set up attached only to the private network, with or without Floating IP. 

If your VM does not have an external IP, you will have to provision a new one. Follow the steps in Provision a new instance - web to provision a new Virtual Machine, taking care of enabling the data network besides public or private.

Reconfigure the existing instance

  1. In the web portal, go to Provision - Instances and click on the instance you want to fix.
  2. Click on the ACTIONS button on the upper-right side, and select Reconfigure from the drop-down menu.
  3. Add the missing data network from the list of networks, after public or private.
    Image Removed

...

making sure that the VM will be reachable on a public IP, either by attaching it to the external-internet public network, or giving it a floating ip if only attached to the private one.

If your VM its setup attached to the external-internet public network, then everything should work from now

Additional steps for VMs with Floating IPs

If your VM is setup with a private network and external Floating IP, then you will need to tell the mars client what your IP address is via the following environment variable:

No Format
export MARS_DHS_LOCALHOST=<your_public_ip>

You will need to have that variable defined on every session that you need to run MARS from. You may add that definition into your .bashrc or .profile scripts.

Content by Label
showLabelsfalse
max5
spacesEWCLOUDKB
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("mars","data","network") and type = "page" and space = "EWCLOUDKB"
labelsmars data network

...