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

MATLAB Parallel Server

I have an MDCS cluster comprised of Linux/Unix worker nodes which uses the MathWorks JobManager (mdce service). I would like to configure the mdce service to start automatically when the nodes boot.

Best Answer

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

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: Is it possible to use mixed client-cluster OS with PBSPro with Parallel Computing toolbox 3.3 (R2008a)

Due to difficulties in setting up uniform permissions for PBS Pro clusters involving Windows client machines and UNIX cluster machines, the Parallel Computing Toolbox does not support this configuration. In cases where PBS Pro is set up so that Windows machines can submit directly to a UNIX cluster, the attached files allow submission from the Windows client machines. In this case, it is necessary to have a shared filesystem between the Windows submission machines and the UNIX cluster machines. Also, the “getDebugLog” function of the scheduler object will have reduced functionality because there may be difficulties in delivering the output files from the cluster back to the client machine.

Here are the steps:

1. Find the $MATLABROOT directory where $MATLABROOT is the MATLAB root directory on your machine, as returned by typing

matlabroot

at the MATLAB Command Prompt.

2. Quit MATLAB.

3. Copy the matlabroot\toolbox\distcomp directory for backup and save it as matlabroot\toolbox\distcomp_nopatch where matlabroot has the value of the directory found in step 1.

4. Unzip the archive to extract the files to matlabroot\toolbox\distcomp directory. The following files should be overwritten by the archive:

@distcomp\@pbsscheduler\pSetClusterOsType.m

bin\util\pbs\execute.sh

bin\util\pbs\header.sh

bin\util\pbs\job-array-prologue.sh

bin\util\pbs\nonshared-copyin.sh

bin\util\pbs\nonshared-copyout.sh

bin\util\pbs\pbsParallelWrapper.sh

bin\util\pbs\rcp.sh

5. Restart MATLAB

6. After restarting MATLAB, issue the following command at the MATLAB Command Prompt to test the mixed cluster:

sched = findResource('scheduler','type','pbspro')   
DataLocation = struct('pc',  'XXX', ... 
           'unix','YYY); % where XXX is the Window path to the DataLocation directory for the client and YYY is the Unix or Linux path to the DataLocation directory for the cluster.
set(sched, 'DataLocation', DataLocation); 
set(sched, 'HasSharedFileSystem', true); 
set(sched, 'ClusterMatlabRoot', 'ML'); %where ML is MATLAB root for cluster
set(sched, 'ClusterOSType', 'unix'); 
job = createJob(sched); 
createTask(job, 'rand', 1, {5}) 
submit(job) 
waitForState(job); 
getAllOutputArguments(job)

Best Answer

Related Solutions

MATLAB: Do mdce boot scripts fail on Fedora distributions

MATLAB: Is it possible to use mixed client-cluster OS with PBSPro with Parallel Computing toolbox 3.3 (R2008a)

Related Question