matlabpool hangs on local scheduler for PCT 5.2 with Internet active Internet connection

I'm trying to run my 1st PCT script. The entire script is:

matlabpool open local 4
c=zeros(1000,4);
parfor i=1:4,
    c(:,i)=eig(rand(1000));
end
matlabpool CLOSE;

When I start this script it hangs on matlabpool. What's wrong here?

Mike

[Kaustubha Govind]

Mike: There might be some issue with your configuration. I recommend contacting MathWorks Tech Support regarding this issue.

Answer 1

[Jason Ross]

If you run the Configuration Validator (Parallel menu, manage configurations, select "local", and validate it), does it validate successfully?

Also, if you look st the processes running on your machine, do additional MATLAB processes start?

Beyond that, please contact support. There should really be nothing "extra" to do to make the local scheduler work.

[Michael]

Jason and Kaustubha,

Thank you both for your comments and answers. I've discovered that starting Matlab from the Start menu, 'ver' shows the Parallel Computing Toolbox, yet if I start Matlab from a shortcut on my desktop (which points to the same target, but a different starting folder), 'ver' does not show the PCT. Furthermore the Configuration Validator validates successfully when Matlab is started from the Start menu, however the above script still hangs on matlabpool. Multiple copies of Matlab processes do appear in the task manager, yet the system resources are not taxed. (This machine is an i7 with 16GB of RAM. The 'C' drive is a RAID 5 of 4 64GB SSD's, the 'D' drive is a 2TB disk. I am nowhere near my resource limits in the task manager (CPU 0%, Mem 2.21GB). You have both suggested 'punt' and ask for help. I think you are both RIGHT!

Answer 2

[Michael]

Patrick Sullivan (Mathworks Installation and Licensing Specialist) correctly identified this issue as a Toolbox visibility issue. The following Matlab commands fixed the issue:

Issue the following Matlab commands: >> restoredefaultpath >> userpath reset >> savepath Exit, then restart Matlab.

Evidently these commands restore the visibility of all licensed toolboxes. (Very handy thing to know...)