Failed to validate a local parallel cluster in MATLAB 2021b

17 vues (au cours des 30 derniers jours)
Sergio U
Sergio U le 3 Oct 2021
Commenté : Stefano Petrò le 14 Mar 2022
When I try to validate the local cluster I have an error, this is the report of the validation.
VALIDATION REPORT
Profile: local
Scheduler Type: Local
Stage: Cluster connection test (parcluster)
Status: Passed
Start Time: Sun Oct 03 12:04:18 CDT 2021
Finish Time: Sun Oct 03 12:04:18 CDT 2021
Running Duration: 0 min 0 sec
Description:
Error Report:
Command Line Output:
Debug Log:
Stage: Job test (createJob)
Status: Failed
Start Time: Sun Oct 03 12:04:18 CDT 2021
Finish Time: Sun Oct 03 12:04:19 CDT 2021
Running Duration: 0 min 1 sec
Description: Job errored or did not reach the state 'finished'.
Error Report: Job errored or did not reach the state 'finished'.
Command Line Output:
Debug Log: LOG FILE OUTPUT:
Stage: SPMD job test (createCommunicatingJob)
Status: Passed
Start Time: Sun Oct 03 12:04:19 CDT 2021
Finish Time: Sun Oct 03 12:05:25 CDT 2021
Running Duration: 1 min 6 sec
Description: Job ran with 6 workers.
Error Report:
Command Line Output:
Debug Log:
Stage: Pool job test (createCommunicatingJob)
Status: Passed
Start Time: Sun Oct 03 12:05:26 CDT 2021
Finish Time: Sun Oct 03 12:06:31 CDT 2021
Running Duration: 1 min 5 sec
Description: Job ran with 6 workers.
Error Report:
Command Line Output:
Debug Log:
Stage: Parallel pool test (parpool)
Status: Failed
Start Time: Sun Oct 03 12:06:32 CDT 2021
Finish Time: Sun Oct 03 12:06:44 CDT 2021
Running Duration: 0 min 13 sec
Description: Failed to initialize the interactive session.
Error Report: Failed to initialize the interactive session.
Caused by:
Error using parallel.internal.pool.AbstractInteractiveClient>iThrowIfBadParallelJobStatus (line 426)
The interactive communicating job failed with no message.
Command Line Output:
Debug Log: CLIENT LOG OUTPUT
Checking communicating job status.
Job state is 'failed'.
No task error messages.
Communicating job debug log:
LOG FILE OUTPUT:
Session failed to start when creating InteractiveClient. Error: Error using parallel.internal.pool.AbstractInteractiveClient>iThrowWithCause (line 305)
Failed to initialize the interactive session.
Error in parallel.internal.pool.AbstractInteractiveClient/start (line 142)
iThrowWithCause( 'parallel:convenience:FailedToInitializeInteractiveSession', err );
Error in parallel.internal.pool.AbstractClusterPool>iStartClient (line 831)
spmdInitialized = client.start(sessionBuildFcn, sessionInfo, numWorkers, cluster, ...
Error in parallel.internal.pool.AbstractClusterPool.hBuildPool (line 585)
iStartClient(client, sessionInfo, forceSpmdEnabled, cluster, supportRestart, argsList);
Error in parallel.internal.types.ValidationStages>iOpenPoolForCluster (line 456)
aPool = parallel.internal.pool.AbstractClusterPool.hBuildPool('Cluster', cluster, 'NumWorkers', numWorkers);
Error in parallel.internal.types.ValidationStages>@()iOpenPoolForCluster(runInfo)
Error in parallel.internal.types.ValidationStages>iCallWithNoHotlinks (line 336)
[varargout{1:nargout}] = fcn();
Error in parallel.internal.types.ValidationStages>iRunParpoolStage (line 247)
[commandWindowOutput, aPool] = evalc(iWrapForEvalc(openPoolFcn));
Error in parallel.internal.types.ValidationStages/run (line 68)
[eventData, runInfo] = obj.RunFunction(obj, runInfo);
Error in parallel.internal.validator.Validator/runValidationSuite (line 191)
[eventData, stageRunInfo] = currentStage.run(stageRunInfo);
Error in parallel.internal.validator.Validator/validate (line 103)
status = obj.runValidationSuite(profileName, suite);
Error in parallel.internal.ui.AbstractValidationManager/validate (line 36)
obj.Validator.validate(profileName, validationSuite);
Error in parallel.internal.ui.ValidationManager.validateProfile (line 36)
parallel.internal.ui.ValidationManager.getOrCreateInstance().validate(profileName, suite);
Caused by:
Error using parallel.internal.pool.AbstractInteractiveClient>iThrowIfBadParallelJobStatus (line 426)
The interactive communicating job failed with no message.
Failed to run the DisarmableOncleanup callback due to the following error:
Dot indexing is not supported for variables of this type.
I have searched for a solution and tried this code, but didn't work.
distcomp.feature( 'LocalUseMpiexec', false )
And I tried restoring the matlab path but also didn't work.
Does anyone know how I can solve this problem? Thanks in advance!
  2 commentaires
Raymond Norris
Raymond Norris le 3 Oct 2021
I would suggest contacting Technical Support (support@mathworks.com).
Joan Cardona
Joan Cardona le 5 Jan 2022
Hi guys, I got the same problem, did you find the solution?

Connectez-vous pour commenter.

Réponses (1)

Stefano Petrò
Stefano Petrò le 3 Déc 2021
Modifié(e) : Walter Roberson le 5 Jan 2022
Same problem here. Currently waiting for tech support.
VALIDATION REPORT
Profile: local
Scheduler Type: Local
Stage: Cluster connection test (parcluster)
Status: Passed
Start Time: Thu Dec 02 17:31:26 CET 2021
Finish Time: Thu Dec 02 17:31:29 CET 2021
Running Duration: 0 min 2 sec
Description:
Error Report:
Command Line Output:
Debug Log:
Stage: Job test (createJob)
Status: Failed
Start Time: Thu Dec 02 17:31:29 CET 2021
Finish Time: Thu Dec 02 17:31:33 CET 2021
Running Duration: 0 min 4 sec
Description: Job errored or did not reach the state 'finished'.
Error Report: Job errored or did not reach the state 'finished'.
Command Line Output:
Debug Log: LOG FILE OUTPUT:
Stage: SPMD job test (createCommunicatingJob)
Status: Passed
Start Time: Thu Dec 02 17:31:33 CET 2021
Finish Time: Thu Dec 02 17:32:04 CET 2021
Running Duration: 0 min 31 sec
Description: Job ran with 4 workers.
Error Report:
Command Line Output:
Debug Log:
Stage: Pool job test (createCommunicatingJob)
Status: Passed
Start Time: Thu Dec 02 17:32:05 CET 2021
Finish Time: Thu Dec 02 17:32:39 CET 2021
Running Duration: 0 min 33 sec
Description: Job ran with 4 workers.
Error Report:
Command Line Output:
Debug Log:
Stage: Parallel pool test (parpool)
Status: Failed
Start Time: Thu Dec 02 17:32:40 CET 2021
Finish Time: Thu Dec 02 17:32:52 CET 2021
Running Duration: 0 min 12 sec
Description: Failed to initialize the interactive session.
Error Report: Failed to initialize the interactive session.
Caused by:
Error using parallel.internal.pool.AbstractInteractiveClient>iThrowIfBadParallelJobStatus (line 426)
The interactive communicating job failed with no message.
Command Line Output:
Debug Log: CLIENT LOG OUTPUT
Checking communicating job status.
Job state is 'failed'.
No task error messages.
Communicating job debug log:
LOG FILE OUTPUT:
Session failed to start when creating InteractiveClient. Error: Error using parallel.internal.pool.AbstractInteractiveClient>iThrowWithCause (line 305)
Failed to initialize the interactive session.
Error in parallel.internal.pool.AbstractInteractiveClient/start (line 142)
iThrowWithCause( 'parallel:convenience:FailedToInitializeInteractiveSession', err );
Error in parallel.internal.pool.AbstractClusterPool>iStartClient (line 831)
spmdInitialized = client.start(sessionBuildFcn, sessionInfo, numWorkers, cluster, ...
Error in parallel.internal.pool.AbstractClusterPool.hBuildPool (line 585)
iStartClient(client, sessionInfo, forceSpmdEnabled, cluster, supportRestart, argsList);
Error in parallel.internal.types.ValidationStages>iOpenPoolForCluster (line 456)
aPool = parallel.internal.pool.AbstractClusterPool.hBuildPool('Cluster', cluster, 'NumWorkers', numWorkers);
Error in parallel.internal.types.ValidationStages>@()iOpenPoolForCluster(runInfo)
Error in parallel.internal.types.ValidationStages>iCallWithNoHotlinks (line 336)
[varargout{1:nargout}] = fcn();
Error in parallel.internal.types.ValidationStages>iRunParpoolStage (line 247)
[commandWindowOutput, aPool] = evalc(iWrapForEvalc(openPoolFcn));
Error in parallel.internal.types.ValidationStages/run (line 68)
[eventData, runInfo] = obj.RunFunction(obj, runInfo);
Error in parallel.internal.validator.Validator/runValidationSuite (line 191)
[eventData, stageRunInfo] = currentStage.run(stageRunInfo);
Error in parallel.internal.validator.Validator/validate (line 103)
status = obj.runValidationSuite(profileName, suite);
Error in parallel.internal.ui.AbstractValidationManager/validate (line 36)
obj.Validator.validate(profileName, validationSuite);
Error in parallel.internal.ui.ValidationManager.validateProfile (line 36)
parallel.internal.ui.ValidationManager.getOrCreateInstance().validate(profileName, suite);
Caused by:
Error using parallel.internal.pool.AbstractInteractiveClient>iThrowIfBadParallelJobStatus (line 426)
The interactive communicating job failed with no message.
Failed to run the DisarmableOncleanup callback due to the following error:
Dot indexing is not supported for variables of this type.
  3 commentaires
Raymond Norris
Raymond Norris le 12 Mar 2022
@Heinz Miranda, please contact Technical Support (support@mathworks.com).
Stefano Petrò
Stefano Petrò le 14 Mar 2022
Actually, In my case the issue depended on my surname, which contains an accent mark (I am Italian, BTW). As this was also in my home directory path, and the latest release of Matlab being unable to handle it (differing from previous releases), I had to change my home directory path (which actually made a few other apps to malfunction). In the end this was filed as a bug to solve - and I am afraid this is not helpful to you.
Nevertheless, the Matlab team also suggested me this workaround (after I changed my home directory path - never tried it):
They have provided an alternative workaround which is to start MATLAB with a modified license path using the -c argument. The underlying issue is that the license path contains a non ascii character (the ò) by pointing to the license in a location without that character you will be able to continue using PCT with no issues:
How do I force MATLAB to ignore the LM_LICENSE_FILE environment variable?

Connectez-vous pour commenter.

Produits


Version

R2021b

Community Treasure Hunt

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

Start Hunting!

Translated by