MATLAB: Does “Testing Connectivity” on Admin Center shows “Node Port Availability” as “Test failed.”

MATLAB Parallel Server

I see the "Test failed" icon at "Node Port Availability" when I executed "Testing Connectivity" from Admin Center. How can I resolve this failure?

Testing Connectivity:

http://www.mathworks.com/help/mdce/testing-connectivity.html

Best Answer

This error is caused by a connection issue in the cluster. To resolve this issue, please try the following steps:

1. Verify if Network License Manager is started

Please make sure if the License Manager has been started correctly. Please refer to the related solution "How do I monitor the usage of licenses or keys for MATLAB and the Toolboxes?" if you would likt to know how to verify License Manager status.

2. Verify what port number is used on License Manager

Please make sure if the port number of your network.lic and license.dat for License Manager are the same. If you network.lic file has the different port number, please update this number to the same as license.dat for License Manager.

To make sure about your port number, please refer to the related solution "How do I migrate my MATLAB clients to a new license server when the license server changes?".

3. Firewall

Please make sure if your Firewall prevents the connections as the reasons below.

3-1) The License Server Firewall settings prevent from incoming or outgoing connection through the port number. You are able to verify this affection by disabling Firewall temporary. There are two ports the license manager uses for communication. To make sure about port number in detail, please refer to the realted solution "Can the network license manager be configured to work inside a firewall?".

3-2) One or more nodes in the cluster cannot identify each other and allow its mdce service to communicate with the mdce service on the other cluster nodes. To resolve this issue, please refer to the related solution "How do I configure the MATLAB Parallel Server, Job Manager and Parallel Computing Toolbox to work within a firewall?".

4. Verify the MJS service is started on all nodes

To verify if mjs service is started on all nodes:

http://www.mathworks.com/help/mdce/nodestatus.html

NOTE: Starting in R2019a the following name changes occurred:
MATLAB Distributed Computing Server was renamed to MATLAB Parallel Server
mdce_def was renamed to mjs_def
mdce binary was renamed to mjs

Related Solutions

MATLAB: Do I receive License Manager Error -18

Check the following:

1. Check whether you are using a feature which you do not have a license for.

2. Another common cause of this error is updating your license file without restarting your network license manager. If you administrate the license manager for your license, try restarting the license manager and then try to run MATLAB again. If you do not administrate the license server, contact your administrator to have the license manager restarted.

For more information on how to restart the network license manager, see the Related Solution linked below.

How do I start or stop the Network License Manager?

https://www.mathworks.com/matlabcentral/answers/102968-how-do-i-start-or-stop-the-network-license-manager

3. Update the license file on the client machine to contain only the following two lines (without quotes):

SERVER "hostname" "HostID" "port"

USE_SERVER

"hostname" is the hostname of the license server

"HostID" is the HostID of the license server

"port" is the port that the license manager communicates on

The license file on the client machine varies depending upon operating system and version. For R2008a and above, the license file is generally called network.lic and is located in $MATLAB\licenses (where $MATLAB is the MATLAB installation directory). For versions prior to R2008a, the license file will generally be the following:

Windows

---------

 $MATLAB\bin\win32\license.dat (for 32-bit MATLAB)
 $MATLAB\bin\win64\license.dat (for 64-bit MATLAB)

Linux/Unix/Mac

------------------

 $MATLAB/etc/license.dat

3. If this error is being received on the client, have your license administrator make sure the HostID/IP Address listed in the commented section in the license.dat file matches the HostID/IP Address in the SERVER line.

Additionally, if you get this message on the client it could indicate that the product is not on the license.

4. If this error is occurring on the license manager server, then this error may be the result of having extra carriage returns in your license file. In order to avoid this, ensure that the following strings all begin on a left justified line: #, SERVER, DAEMON, or INCREMENT. Sometimes an INCREMENT line can get wrapped on the end of the preceding INCREMENT line causing it to be omitted.

5. This error could occur if a client computer is attempting to checkout a MATLAB seat from a license manager hosting only an MATLAB Parallel Server license. It could also occur for the opposite scenario, if a MATLAB Parallel Server worker is attempting to checkout a MATLAB Parallel Server seat from a server hosting a MATLAB license.

NOTE: Starting in R2019a the following name changes occurred:

MATLAB Distributed Computing Server was renamed to MATLAB Parallel Server
mdce_def was renamed to mjs_def
mdce binary was renamed to mjs

MATLAB: Am I unable to connect to or locate the MATLAB Parallel Server job manager via a MATLAB Client

These connection errors may be caused by the server running the jobmanager not having a resolvable hostname. This is most often due to the fact that MATLAB Parallel Server machines are not part of the domain and hence do not have a fully qualified domain name. This causes the cluster to be unresolvable by the Distributed Computing Toolbox. All machines (most importantly, the machine which contains the jobmanager) must be domain members and have resolvable names recorded in the network's DNS.

Below, you will find some basic troubleshooting steps to determine the causes of this connection problem:

1. Verify that you are using the correct command to find the jobmanager.

Examples:

a. Find any job manager available:

               jm = findResource('jobmanager')

b. Find a specific named job manager:

              jm = findResource('jobmanager', 'name', 'MyJobManager')

c. Use a UNICAST call to the job manager machine:

              jm = findResource('jobmanager', 'LookupURL', 'hostname or IPaddress')

- If there is a connection error between the client and the job manager machine, you will likely see a "handle 0 by 1" message returned. If this occurs, check the jobmanager name and hostname.

2. Check basic networking connections between the client and job manager node.

- From the client machine, verify if you can ping, traceroute and nslookup to the job manager node and vice-versa. The client machine must know the name of the job manager machine via DNS or some type of lookup service. If this fails, there is a networking problem that must be resolved by your IT staff.

3. Check the hostnames of the jobmanager and client machines using a MATLAB session. If any of these tests fail, refer to your system administrator resolve the network issue.

-On both the client and the jobmanager machine what does the following MATLAB command return:

java.net.InetAddress.getLocalHost.getHostName

This should be the short names but might not be (some PC's think their name is different than the DNS name). For example:

>> java.net.InetAddress.getLocalHost.getHostName
ans =
johns-computer

4. Check to make sure that a firewall program is not blocking the ports MATLAB Parallel Server uses. By default MATLAB Parallel Server uses ports 27350 through 27350 + N (where N is the number of worker nodes in your cluster). If it is, refer to the attached solution below.

Also, check for other firewalled sockets on the jobmanager.

- Run the following command as root:

iptables -L

At this point, if you need further assistance, send the following information to

www.mathworks.com/contact_TS.html

- Operating System information

- A brief explanation of the issue and how to reproduce it.

- Log files from the jobmanager machine. By default these are located in /var/log/mdce on UNIX/MAC machines or in $TEMP/MDCE/Log on Windows machines.

NOTE: Starting in R2019a the following name changes occurred: - MATLAB Distributed Computing Server was renamed to MATLAB Parallel Server

- mdce_def was renamed to mjs_def

- mdce binary was renamed to mjs

Best Answer

Related Solutions

MATLAB: Do I receive License Manager Error -18

MATLAB: Am I unable to connect to or locate the MATLAB Parallel Server job manager via a MATLAB Client

Related Question