Error in using 'parpool'

43 views (last 30 days)
Simon Oh
Simon Oh on 6 Oct 2016
Commented: shreya on 31 Aug 2018
Hi, I have been using parpool to run my function simultaneously. However, in my new laptop, I got the problem as follows:
>> parpool('local', noPMrun);
Starting parallel pool (parpool) using the 'local' profile ...
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 665)
Failed to start pool.
Error using parallel.Cluster/createCommunicatingJob (line 92)
ICU error: get canonical time zone ID, err='U_ILLEGAL_ARGUMENT_ERROR'.
Is there anyone who can help/solve this problem? Thank you
Maxim Ovechkin
Maxim Ovechkin on 2 Aug 2017

Amazing. Thank you, Clint!

Sign in to comment.

Answers (5)

Zygmunt Szpak
Zygmunt Szpak on 24 Feb 2017
Edited: Zygmunt Szpak on 24 Feb 2017
I encountered the same problem. My workaround was to set the TZ environment variable to:
export TZ='Australia/Adelaide'
You can find the correct timezone string for your location here:

Prasad Mendu
Prasad Mendu on 17 Oct 2016
Does the validation of the local cluster profile succeed? For more information on how to validate, refer to the link below:
Local cluster profile uses the cores on your machine to parallelize the code and it could be possible that there are validation errors with local profile on your new laptop, and it will be helpful to look at those errors to know the cause of this issue.

Peter Perkins
Peter Perkins on 16 Feb 2017
Norm, Clint, Artem, and Simon, what if anything is your TZ environment variable set to, and what does /etc/localtime point to? If you symlink /etc/localtime to, say, /usr/share/zoneinfo/Etc/UTC, does the problem go away?
Setting TZ should work around this problem. If you can do that, it's probably a better idea than modifying datetime.m.

orlem lima dos santos
orlem lima dos santos on 12 Dec 2017
After looking inside datetime function I realized that matlab gets the timezone from the computer. So all you need to do is fix the timezone from your computer and reopen matlab it should works after this.
It is works for me.
shreya on 31 Aug 2018
Thanks.. This work-around helps!

Sign in to comment.

Daniel Melnick
Daniel Melnick on 26 Jan 2018
I have the same problem while trying to run the parallel toolbox on a Mac Pro running High Sierra. Please help
  1 Comment
Peter Perkins
Peter Perkins on 31 Jan 2018
Daniel, High Sierra changed the organization of the system time zone files, resulting in symptoms that look like the ones described for Linux in the bug report I posted above, but for a completely different reason.
R2017b and earlier suffer from this, but there is a bug report with a work-around that will work for those versions of MATLAB.

Sign in to comment.


Community Treasure Hunt

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

Start Hunting!