Failed to start a parallel pool in matlab2015a

Hi, I have tried parpool and it ended as:
-----------------
Error using parpool (line 103)
Failed to start a parallel pool. (For information in addition to the
causing error, validate the profile 'local' in the Cluster Profile
Manager.)
Caused by:
Error using parallel.internal.pool.InteractiveClient>iThrowWithCause
(line 667)
Failed to initialize the interactive session.
Error using
parallel.internal.pool.InteractiveClient>iThrowIfBadParallelJobStatus
(line 768)
The interactive communicating job failed with no message.
----------
I then tried to validate the profile 'local', and got these details:
----------
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: Passed
Description:Validation Passed
Command Line Output:(none)
Error Report:(none)
Debug Log:(none)
Stage: SPMD job test (createCommunicatingJob)
Status: Failed
Description:The job errored or did not reach state finished.
Command Line Output:(none)
Error Report:(none)
Debug Log:
LOG FILE OUTPUT:
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: Parallel pool test (parpool)
Status: Skipped
Description:Validation skipped due to previous failure.
Command Line Output:(none)
Error Report:(none)
Debug Log:(none)
-------
I have searched for answered and tried to close my computer firewall but it didn't work. Does anyone know how to solve this problem? Thanks in advance!

1 comentario

Edric Ellis
Edric Ellis el 8 de Abr. de 2015
I suggest you contact MathWorks technical support to resolve installation problems like this.

Iniciar sesión para comentar.

 Respuesta aceptada

Jason Fice
Jason Fice el 14 de Jul. de 2015

4 votos

I had the same error, and validation results. I contacted Mathworks for help and their suggestion was simple and worked for me. See below for an excerpt from their response to me:
"Thank you for contacting MathWorks Installation and Licensing Support. If you are experiencing issues with opening parpool with the local cluster, you may be having issues with the new local mpiexec implementation. It may not woork on all hardware and software configurations. Try the following command to disable this feature:
distcomp.feature( 'LocalUseMpiexec', false )
If this resolves the issue, add the line to your startup.m file. If you do not have a startup.m, create a new file called startup.m in your MATLAB startup directory and add the above line.
Disabling the local mpiexec will not slow down parpool operation but it may make parpool open more slowly. The decrease in efficacy is negligible"

4 comentarios

Martin Muller
Martin Muller el 21 de Dic. de 2015
Editada: Martin Muller el 21 de Dic. de 2015
I just had the same problem.
distcomp.feature( 'LocalUseMpiexec', false )
didn't resolve my issue, but
distcomp.feature( 'LocalUseMpiexec', true )
did. Thanks for this hint. I add it to my startup.m script.
This solved my problem:
distcomp.feature( 'LocalUseMpiexec', false )
Thanks!
Muahammad Younas
Muahammad Younas el 10 de Feb. de 2018
hi everyone.... i have the same problem using matlab (2015a)... i am not able to solve the problem with above mentioned method... while putting "distcomp.feature( 'LocalUseMpiexec', false )" in "startup.m". Access denied answer is shown to me..... Please help me ...
Amany Arafa
Amany Arafa el 22 de Mzo. de 2018
Run Matlab as Administrator so you can start parpool

Iniciar sesión para comentar.

Más respuestas (4)

Tao Wang
Tao Wang el 13 de Jul. de 2018
Editada: Tao Wang el 13 de Jul. de 2018

1 voto

Hi Mathworks,
I have a similar issue (matlab R2018a), but the solution "distcomp.feature( 'LocalUseMpiexec', false )" does not work for me.
Here is the Cluster profile report. Any ideas?
VALIDATION REPORT Profile: local Scheduler Type: Local
Stage: Cluster connection test (parcluster) Status: Passed Start Time: Fri Jul 13 12:55:45 PDT 2018 Finish Time: Fri Jul 13 12:55:45 PDT 2018 Running Duration: 0 min 0 sec Description: Error Report: Command Line Output: Debug Log:
Stage: Job test (createJob) Status: Failed Start Time: Fri Jul 13 12:55:45 PDT 2018 Finish Time: Fri Jul 13 12:55:45 PDT 2018 Running Duration: 0 min 0 sec Description: An unexpected error occurred accessing properties: "AdditionalPaths" "ApiTag" "AttachedFileData" "AttachedFilePaths" "AttachedFiles" "AutoAttachFiles" "AutoAddClientPath" "CreateDateTime" "CreateTime" "DependentFiles" "EnvironmentVariables" "ExecutionMode" "FinishDateTime" "FinishTime" "JobData" "MATLABDrivePathMap" "Name" "NumPathsToAppend" "NumThreads" "ProductKeys" "StartDateTime" "StartTime" "StateEnum" "SubmitDateTime" "SubmitTime" "Tag" "Username" "Version" "JobSchedulerData" Error Report: An unexpected error occurred accessing properties: "AdditionalPaths" "ApiTag" "AttachedFileData" "AttachedFilePaths" "AttachedFiles" "AutoAttachFiles" "AutoAddClientPath" "CreateDateTime" "CreateTime" "DependentFiles" "EnvironmentVariables" "ExecutionMode" "FinishDateTime" "FinishTime" "JobData" "MATLABDrivePathMap" "Name" "NumPathsToAppend" "NumThreads" "ProductKeys" "StartDateTime" "StartTime" "StateEnum" "SubmitDateTime" "SubmitTime" "Tag" "Username" "Version" "JobSchedulerData"
Caused by: Error using assert Too many input arguments. Command Line Output: Debug Log:
Stage: SPMD job test (createCommunicatingJob) Status: Failed Start Time: Fri Jul 13 12:55:45 PDT 2018 Finish Time: Fri Jul 13 12:55:45 PDT 2018 Running Duration: 0 min 0 sec Description: An unexpected error occurred accessing properties: "AdditionalPaths" "ApiTag" "AttachedFileData" "AttachedFilePaths" "AttachedFiles" "AutoAttachFiles" "AutoAddClientPath" "CreateDateTime" "CreateTime" "DependentFiles" "EnvironmentVariables" "ExecutionMode" "FinishDateTime" "FinishTime" "JobData" "MATLABDrivePathMap" "Name" "NumPathsToAppend" "NumThreads" "ProductKeys" "StartDateTime" "StartTime" "StateEnum" "SubmitDateTime" "SubmitTime" "Tag" "Username" "Version" "JobSchedulerData" "MinNumWorkers" "MaxNumWorkers" Error Report: An unexpected error occurred accessing properties: "AdditionalPaths" "ApiTag" "AttachedFileData" "AttachedFilePaths" "AttachedFiles" "AutoAttachFiles" "AutoAddClientPath" "CreateDateTime" "CreateTime" "DependentFiles" "EnvironmentVariables" "ExecutionMode" "FinishDateTime" "FinishTime" "JobData" "MATLABDrivePathMap" "Name" "NumPathsToAppend" "NumThreads" "ProductKeys" "StartDateTime" "StartTime" "StateEnum" "SubmitDateTime" "SubmitTime" "Tag" "Username" "Version" "JobSchedulerData" "MinNumWorkers" "MaxNumWorkers"
Caused by: Error using assert Too many input arguments. Command Line Output: Debug Log:
Stage: Pool job test (createCommunicatingJob) Status: Skipped Start Time: Finish Time: Running Duration: Description: Validation skipped due to previous failure. Error Report: Command Line Output: Debug Log:
Stage: Parallel pool test (parpool) Status: Skipped Start Time: Finish Time: Running Duration: Description: Validation skipped due to previous failure. Error Report: Command Line Output: Debug Log:

8 comentarios

po,gpo,eoeo
po,gpo,eoeo el 6 de Dic. de 2018
similar problems 2018b
Star Rats
Star Rats el 10 de Abr. de 2019
Editada: Star Rats el 10 de Abr. de 2019
This works for my case:
For Windows:
Go to the Start Menu and select Run.
Type in %APPDATA% and press Enter.
For Microsoft Windows Vista:
Type in %APPDATA% in the "Start Search" field above the Start menu and press Enter.
From the Application Data folder, go to MathWorks to MATLAB.
Rename or delete the folder "local_scheduler_data" (when working with MATLAB versions prior to R2012a) or "local_cluster_jobs" (when working with MATLAB R2012a and newer).
Once cleared, try restarting MATLAB.
Source: here
shree hARI NAIR
shree hARI NAIR el 3 de Mzo. de 2020
thanks you star rat it worked
haseeb qureshi
haseeb qureshi el 25 de Mzo. de 2020
Cheers Star Rats, your solution worked for me. You're a star!
Snigdha
Snigdha el 26 de Sept. de 2020
Thanks Star Rats. Your solution actually helped me.
ying ying
ying ying el 29 de Dic. de 2020
Thanks for your idea!
Armin Mashhadi
Armin Mashhadi el 22 de Mayo de 2021
That worked. Thank you very very much <3
Walter Roberson
Walter Roberson el 13 de Jul. de 2021
伟杰 白 comments to Star Rats:
this works

Iniciar sesión para comentar.

Mininath Bendre
Mininath Bendre el 25 de Abr. de 2016

0 votos

Thanks a lot Jason Fice and Martin Muller,
distcomp.feature( 'LocalUseMpiexec', false )
This one works........
shuai li
shuai li el 18 de Abr. de 2019

0 votos

I got some other issues. The parallel pool starts normally with small number of workers set. Commands parpool(4) and parpool(6) works well. But when the number of workers increases, command parpool(10) cannot start the pool correctly, and gives the following errors:
Error using parpool (line 113)
Parallel pool failed to start with the following error. For more detailed
information, validate the profile 'local' in the Cluster Profile Manager.
Caused by:
Error using parallel.internal.pool.InteractiveClient>iThrowWithCause
(line 678)
Failed to initialize the interactive session.
Error using
parallel.internal.pool.InteractiveClient>iThrowIfBadParallelJobStatus
(line 792)
The interactive communicating job failed with no message.
Does anyone know how to fix the problem?
Thanks!

3 comentarios

Jordan Makansi
Jordan Makansi el 2 de Jul. de 2021
Editada: Jordan Makansi el 2 de Jul. de 2021
Hi shuai li, were you able to fix this? I have the same problem on matlab 2020b, and almost exact same error message;
^HError using parallel.Cluster/parpool (line 86)
Parallel pool failed to start with the following error. For more detailed information, create a profile for your cluster and validate the profile in the Cluster Profile Manager.
Caused by:
Error using parallel.internal.pool.InteractiveClient>iThrowWithCause (line 678)
Failed to initialize the interactive session.
Error using parallel.internal.pool.InteractiveClient>iThrowIfBadParallelJobStatus (line 816)
The interactive communicating job failed with no message.
}^H
ans =
logical
1
Starting parallel pool (parpool) ...
I tried
distcomp.feature( 'LocalUseMpiexec', false )
and also tried
distcomp.feature( 'LocalUseMpiexec', true )
Still same error.
Were you able to fix it?
Vu Minh
Vu Minh el 24 de En. de 2022
Run Matlab as Administrator, It could work
Andrew Davies
Andrew Davies el 25 de Abr. de 2024
Try this
https://www.mathworks.com/support/bugreports/2968710

Iniciar sesión para comentar.

Nik Gap
Nik Gap el 22 de Abr. de 2020
I have got another problem: only the last stage failed (Parallel pool test). Error: Failed to locate and destroy old interactive jobs.
What should I do?
VALIDATION REPORT
Profile: local
Scheduler Type: Local
Stage: Cluster connection test (parcluster)
Status: Passed
Start Time: Wed Apr 22 13:31:21 CEST 2020
Finish Time: Wed Apr 22 13:31:21 CEST 2020
Running Duration: 0 min 0 sec
Description:
Error Report:
Command Line Output:
Debug Log:
Stage: Job test (createJob)
Status: Passed
Start Time: Wed Apr 22 13:31:21 CEST 2020
Finish Time: Wed Apr 22 13:31:33 CEST 2020
Running Duration: 0 min 13 sec
Description:
Error Report:
Command Line Output:
Debug Log:
Stage: SPMD job test (createCommunicatingJob)
Status: Passed
Start Time: Wed Apr 22 13:31:34 CEST 2020
Finish Time: Wed Apr 22 13:31:51 CEST 2020
Running Duration: 0 min 18 sec
Description: Job ran with 28 workers.
Error Report:
Command Line Output:
Debug Log:
Stage: Pool job test (createCommunicatingJob)
Status: Passed
Start Time: Wed Apr 22 13:31:51 CEST 2020
Finish Time: Wed Apr 22 13:32:14 CEST 2020
Running Duration: 0 min 23 sec
Description: Job ran with 28 workers.
Error Report:
Command Line Output:
Debug Log:
Stage: Parallel pool test (parpool)
Status: Failed
Start Time: Wed Apr 22 13:32:15 CEST 2020
Finish Time: Wed Apr 22 13:32:15 CEST 2020
Running Duration: 0 min 1 sec
Description: Failed to locate and destroy old interactive jobs.
Error Report: Failed to locate and destroy old interactive jobs.
Caused by:
Error using parallel.Cluster/findJob (line 74)
Unknown type: concurrentconcurrentconcurrent.
Command Line Output:
Debug Log:

Categorías

Preguntada:

el 7 de Abr. de 2015

Comentada:

el 25 de Abr. de 2024

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by