MATLAB: Does the MDCS 3.3 (MATLAB Distributed Computing Server R2008a) or newer service fail to start on the Linux machine

MATLAB Parallel Server

I am setting up the MATLAB Distributed Computing Server service on my Linux machine in order to run the jobmanager and workers. After I start the MDCS service, I am unable to start a jobmanager or worker. When I check nodestatus, it states that the service is not running.

Best Answer

This issue is generally caused when the MDCS service is started on a machine that is not configured with glibc version 2.3.6 or higher. MATLAB 7.6 (R2008a) and newer are built using glibc 2.3.6, and machines that run glibc 2.3.4 (e.g. RHEL 4) cause MATLAB to prompt the user to continue in order to run MATLAB. This prompt fails to display when starting the MDCS service.

In order to bypass the prompt and allow the MDCS service to start, replace the file

$MATLABROOT/bin/util/oscheck.sh

(where $MATLABROOT is the MATLAB root directory) with the attached file and restart the MDCS service.

For more information about the glibc warning, see the Related Solution listed below.

If you are upgrading to a newer version of MDCS, make sure you stopped the old service and cleared the temporary files:

1. Log in as root.

2. On each cluster node, stop the mdce service by typing the commands

cd oldmatlabroot/toolbox/distcomp/bin
./mdce stop

3. On each cluster node, delete the existing log and checkpoint directories or their contents. By default, these directories are:

/var/log/mdce
/var/lib/mdce

Related Solutions

MATLAB: Do mdce boot scripts fail on Fedora distributions

This change has been incorporated into the documentation in Release 2012a (R2012a). For previous releases, read below for any additional information:

Most recent versions of Fedora are built using a different directory structure for boot scripts. In particular, they have moved away from SystemV to Upstart and SystemD. In this case, Fedora no longer has a /etc/rc.d/ directory, but instead it has /etc/rc#.d, where # is associated with /etc/inittab run level number. Therefore, our setup guide is no longer valid for newer versions of Fedora. In order to avoid this problem please follow the steps below.

On each cluster node, register the mdce service as a known service and

configure it to start automatically at system boot time by following these steps:

1. Create the following link, if it does not already exist:

ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/mdce

2. Create the following link to the boot script file:

ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/init.d/mdce

3. Set boot script file permissions:

chmod 555 /etc/init.d/mdce

4. Look in /etc/inittab for the default run level. Create a link in the rc

folder associated with that run level. For example, if the run level is 5,

execute these commands:

cd /etc/rc5.d;

ln -s ../init.d/mdce S99MDCE

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: How to configure the mdce service to start automatically at boot on Linux/Unix cluster nodes

To configure the mdce service to start at system boot, follow the appropriate instructions below depending on your OS distribution type:

=====

Debian Platform

=====

On each cluster node, register the mdce service as a known service and

configure it to start automatically at system boot time by following these steps:

1. Create the following link, if it does not already exist:

ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/mdce

2. Create the following link to the boot script file:

ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/init.d/mdce

3. Set the boot script file permissions:

chmod 555 /etc/init.d/mdce

4. Look in /etc/inittab for the default run level. Create a link in the rc

directory associated with that run level. For example, if the run level is 5,

execute these commands:

cd /etc/rc5.d;
ln -s ../init.d/mdce S99MDCE

=====

SUSE Platform

=====

On each cluster node, register the mdce service as a known service and

configure it to start automatically at system boot time by following these steps:

1. Create the following link, if it does not already exist:

ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/mdce

2. Create the following link to the boot script file:

ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/init.d/mdce

3. Set the boot script file permissions:

chmod 555 /etc/init.d/mdce

4. Look in /etc/inittab for the default run level. Create a link in the rc

directory associated with that run level. For example, if the run level is 5,

execute these commands:

cd /etc/init.d/rc5.d;
ln -s ../mdce S99MDCE

=====

Red Hat, Fedora Platform

=====

On each cluster node, register the mdce service as a known service and

configure it to start automatically at system boot time by following these steps:

1. Create the following link, if it does not already exist:

ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/mdce

2. Create the following link to the boot script file:

ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/init.d/mdce

3. Set boot script file permissions:

chmod 555 /etc/init.d/mdce

4. Look in /etc/inittab for the default run level. Create a link in the rc

directory associated with that run level. For example, if the run level is 5,

execute these commands:

cd /etc/rc.d/rc5.d;
ln -s ../../init.d/mdce S99MDCE

=====

Solaris Platform

=====

On each cluster node, register the mdce service as a known service and

configure it to start automatically at system boot time by following these steps:

1. Create the following link, if it does not already exist:

ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/mdce

2. Create the following link to the boot script file:

ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/init.d/mdce

3. Set boot script file permissions:

chmod 555 /etc/init.d/mdce

4. Look in /etc/inittab for the default run level. Create a link in the rc

directory associated with that run level. For example, if the run level is 3,

execute these commands:

cd /etc/rc3.d;
ln -s ../init.d/mdce S99MDCE
Instructions for configuring the mdce service to start at boot are included in the Cluster Setup Instructions found at the link below:

http://www.mathworks.com/help/mdce/configure-parallel-computing-products-for-an-mjs.html#bs15wiy-60

Best Answer

Related Solutions

MATLAB: Do mdce boot scripts fail on Fedora distributions

MATLAB: How to configure the mdce service to start automatically at boot on Linux/Unix cluster nodes

Related Question