You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Problem

Your MARS request is stuck, showing messages such as the following:

mars - INFO   - 20200302.105633 - Calling mars on '10.3.165.120', local port is 51714
mars - WARN   - 20200302.105840 - connect : 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

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.

The VM will be restarted as a consequence of this reconfiguration.



  • No labels