MATLAB Answers

0

error using matlabpool

Asked by goutam tulsiyan on 18 Jun 2012
Latest activity Answered by Walter Roberson
on 17 Jul 2015
hi, I am using matlab r2012a on windows 7 (both 64 bit). The processor is Intel Xeon E5620.
When I run matlabpool I get this error:
-----------------------------------------------
Error using matlabpool (line 144) Failed to open matlabpool. (For information in addition to the causing error, validate the profile 'local' in the Cluster Profile Manager.)
Caused by: Error using assert Too many input arguments.
------------------------------------------------
and when I try to validate the profile it does not validte and shows this:
VALIDATION DETAILS Profile: local Scheduler Type: Local
Stage: Cluster connection test (parcluster) Status: Passed Description:Validation Passed Command Line Output:(none) Error Report:(none) Debug Log:(none)
Stage: Job test (createJob) Status: Failed Description:The validation stage encountered a MATLAB exception. Command Line Output:(none) Error Report: Error using parallel.Job/createTask (line 260) Too many input arguments.
Error in parallel.internal.validator.Validator>iCreateAndSubmitJob (line 494) job.createTask(@iGetLabInfo, 2, {});
Error in parallel.internal.validator.Validator/runJobStage (line 265) [commandWindowOutput, job] = evalc('iCreateAndSubmitJob(cluster, jobVariant)');
Error in parallel.internal.validator.Validator/runValidationStages (line 215) currStagePassed = obj.runJobStage(profileName, cluster, currStage);
Error in parallel.internal.validator.Validator/validate (line 111) hasPassed = obj.runValidationStages(profileName);
Error in parallel.internal.ui.ValidationManager/validate (line 45) obj.Validator.validate(profileName); Debug Log:(none)
Stage: SPMD job test (createCommunicatingJob) Status: Failed Description:The validation stage encountered a MATLAB exception. Command Line Output:(none) Error Report: Error using parallel.Job/createTask (line 260) Too many input arguments.
Error in parallel.internal.validator.Validator>iCreateAndSubmitJob (line 494) job.createTask(@iGetLabInfo, 2, {});
Error in parallel.internal.validator.Validator/runJobStage (line 265) [commandWindowOutput, job] = evalc('iCreateAndSubmitJob(cluster, jobVariant)');
Error in parallel.internal.validator.Validator/runValidationStages (line 215) currStagePassed = obj.runJobStage(profileName, cluster, currStage);
Error in parallel.internal.validator.Validator/validate (line 111) hasPassed = obj.runValidationStages(profileName);
Error in parallel.internal.ui.ValidationManager/validate (line 45) obj.Validator.validate(profileName); Debug Log:(none)
Stage: Pool job test (createCommunicatingJob) Status: Skipped Description:Validation skipped due to previous failure. Command Line Output:(none) Error Report:(none) Debug Log:(none)
Stage: MATLAB pool test (matlabpool) Status: Skipped Description:Validation skipped due to previous failure. Command Line Output:(none) Error Report:(none) Debug Log:(none)
Any suggestions are welcome. Thankyou very much for your help.
Regards,
Goutam Hari Tulsiyan, IIIT Hyderabad

  0 Comments

Sign in to comment.

3 Answers

Jason Ross
Answer by Jason Ross
on 18 Jun 2012

The local scheduler should work without any additional setup. I'd suspect that your installation is corrupted or your machine environment is misconfigured in some way.
If you have altered the local cluster setup, try reverting it to default settings and running validation again. You can do this through the Parallel menu.
From the "Error using parallel.Job/createTask (line 260) Too many input arguments", I'd check the system PATH for references to a previous installation of another MATLAB version and also the MATLAB path. It could be that there is a version of that file that's being shadowed and is from a previous version that has a different version of that file.

  0 Comments

Sign in to comment.


miguel
Answer by miguel
on 10 Mar 2014

Try to run matlab from console putting a "sudo" command in front (i.e. sudo /usr/local/MATLAB/your_version/bin/matlab
It could be a permission problem.

  0 Comments

Sign in to comment.


Walter Roberson
Answer by Walter Roberson
on 17 Jul 2015

Checking around, it appears most probably that you have your own assert.m that is being used instead of the MATLAB assert.m . Please check with
which -all assert
and probably the first entry is something you have added to your MATLAB path.

  0 Comments

Sign in to comment.