MATLAB: Does Remote Launcher Configuration hang during installation of PolySpace Client for C/C++ 4.2(R2007a+)

crashPolyspace Client for C/C++

I have a PolySpace Network Concurrent license which includes PolySpace Client for C/C++. I am trying to install PolySpace Client for C/C++ R2007a+ on my desktop machine using the back up PolySpace installer files. It completes the step 1 of installing PS Launcher, Spooler and Viewer in the system desktop.

When I proceed with step 2 of specifying the license.dat, the remote launcher configuration screen just hangs and it does not proceed further.

Best Answer

This occurs when the same port number (#12427) is used for the Server, desktop machine and the Remote Launcher.

To resolve this issue, kindly use same port number (#27000) for the Server and the desktop machine; And also ensure that you use a different port number for the Remote Launcher (#12427 default).

Please see the following files attached below:

 license_Polyspace_desktop.dat
 license_Polyspace_server.dat
 remote_launcher.png

Related Solutions

MATLAB: Does the PolySpace job fail when passed to a Remote Launcher

To begin first verify that the PolySpace server is configured and running properly. To do so:

For Windows:

1. Launch the Remote Launcher Manager tool from the Start menu or by running:

C:\PolySpace\PolySpace_Common\RemoteLauncher\PSTRLManager.exe

2. Check that the configuration is correct

3. Confirm that the log file shows that the service is started by clicking "View Log"

4. If there are any errors or if you are unsure that the service started, click the "Start Daemon" button to restart the service.

For Solaris/Linux:

1. Verify that there is a polyspaced process running

2. Check the log file: /var/PolySpace/polyspaced.log to see that Remote Launcher is started and that there are no errors.

3. If there are any issues, try resetting the Remote Launcher by running the script:

/usr/local/PolySpace/PolySpace_Common/RemoteLauncher/bin/setup-remote-launcher

4. Once reconfigured you can run the same script with the -start-service flag to restart the service:

/usr/local/PolySpace/PolySpace_Common/RemoteLauncher/bin/setup-remote-launcher -start-service

Once you have determined that the service is up and running on the PolySpace Server, check to make sure that the client is configured to point to the correct port on the PolySpace Server. To do so:

1. Open the client Launcher

2. Go to the Options menu to Preferences (R2010a or prior: Edit menu to Preferences)

3. Go to the Remote Launcher tab

4. Choose the option to "Use the following server and port" and enter in the PolySpace Server hostname and port number

5. Press OK to set the PolySpace server

Once set, try running the job once more. If the job still fails, contact the Installation and Licensing Team here:

http://www.mathworks.com/support/contact_us/index.html

MATLAB: What ports are used for communication between Polyspace Clients and Polyspace Server and how can I change it

Five distinct port numbers are available to communicate:

1. The default port number for communication between Polyspace Server/Client or Desktop/Cluster with Polyspace Metrics is 12427.

2. The default port number the Polyspace Client/Desktop communicates with Polyspace Metrics to download results is 12428.

3. The default port number the Polyspace Server/Cluster and the network license manager communicates on is 27000

4. The default port number for tomcat server is 8080

5. Since R2013b, the default port for MATLAB Parallel Server is 27350

See item D for the complete ranges

A. Changing Port number the Polyspace Server/Cluster and Client/Desktop communicate

===========================================

Changing Port On Server during install

When you finish installing the Polyspace Server software, the Polyspace Remote Launcher Manager dialog box opens. Here you can change the port number the Polyspace Server uses to communicate with the Polyspace Client machine. The communication port is set in the Polyspace Remote Launcher Manager on the Polyspace Server at the top of the screen under "Common Settings".\n

Changing Port On Client

By default the PolySpace Client attempts to automatically detect the Polyspace Server host on port number 12427. To set this to be a specific hostname and port number:\n

Open the Polyspace UI
Go to the Options menu to Preferences… (R2010a or prior: Go to the Edit menu to Options>Preferences…)
Go to the Server configuration tab (R2010a or prior: Go to the Remote Launcher tab)
Choose the option to "Use the following server and port" and enter in the PolySpace Server hostname and port number
Press OK to set the PolySpace server

NOTE: If the client cannot find the server, it will give an error "No QueueManager server found"\n

Changing Port On Server Post Installation

If you would like to change this port on the server to not be the default post installation, you can edit the polyspace.conf file: cpu=hostname:portnumber

For example:\n

cpu=polyserver:12490

By default, the polyspace.conf file is found in:

Windows: C:\Polyspace\Polyspace_RLDatas\

Linux: /etc/Polyspace/

For this change to take effect you would need to stop and restart the Polyspace daemon.

B. Changing Port number the Polyspace Client/Desktop communicates with Polyspace Metrics

===================================================

By default the Polyspace Client communicate with Polyspace Metrics on port number 12428. To set this to be a specific port number:\n

Open the Client Graphical User Interface (or PVE)
Go to the Options menu to Preferences… (R2010a or prior: Go to the Edit menu to Options>Preferences…)
Go to the Server configuration tab (R2010a or prior: Go to the Remote Launcher tab)
Choose the option to "Port used to communicate with the Polyspace Metrics web interface" and enter in the port number
Press OK to set the Polyspace new preferences

C. Changing Port number the Polyspace Server/Cluster and network license manager communicate

=====================================================

All MathWorks products communicate the same way with the network license manager. Please look at related Solution

https://www.mathworks.com/matlabcentral/answers/96756-what-ports-does-the-network-license-manager-use-and-how-can-i-set-those-ports

D. Summary of default ports used since R2013b

===================================

Open ports like below if you use one cluster (one MJS and one worker).

Network(License Manager) : 27000 and 1 more port to communicate vendor MLM process. It is random port without assignment, but, you can specify the port number. (Refer to MATLAB answer at this link: https://www.mathworks.com/matlabcentral/answers/96756-what-ports-does-the-network-license-manager-use-and-how-can-i-set-those-ports )
MATLAB Parallel Server (mjs): TCP 27350 through 27359, TCP 28350 through 28352 (one worker)
MATLAB client (PCT) uses ports to connect to the job manager: TCP 27370 through 27470 (Refer to MATLAB answer at this link: https://www.mathworks.com/matlabcentral/answers/94254-how-do-i-configure-matlab-parallel-server-using-the-matlab-job-scheduler-to-work-within-a-firewall )
Polyspace service (polyspaced) : TCP 12427
Polyspace UI communication with Web Metrics : TCP 12428
Tomcat Web Metrics : TCP 8080, TCP 8009, TCP 8005. TCP 8443 is optional, if you want to use HTTPS.

NOTE: Starting in R2019a the following name changes occurred:\n\n

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: Does the PolySpace job fail when passed to a Remote Launcher

MATLAB: What ports are used for communication between Polyspace Clients and Polyspace Server and how can I change it

Related Question