Am 26.07.2019 um 21:12 schrieb Kulshrestha, Vipul via users:

> Hi,
> I am trying to setup my open-mpi application to run under grid.
> It works sometimes, but sometimes I get the below error. I have contacted my 
> grid site administrator and the message from them is that they cannot change 
> the TMPDIR path used in the grid configuration.
> I have tried setting TNPDIR, but it does not help (probably because grid 
> engine resets it).
> What other alternatives do I have?
> One other curious question is that why does open-mpi creates such a large 
> name? I understand that part of this path is dependent on TMPDIR value, but 
> even after that it adds additional unnecessary characters like 
> “openmpi-sessions-<5 digit number>@<machine name>_0/<another 5 digit 
> number>”, which could have been shortened to something like “omp-<5 digit 
> number>@<machine name>_0/<5 digit number>” and saving 14 characters (almost 
> 15% of possible length).
> Thanks,
> Vipul
> PMIx has detected a temporary directory name that results
> in a path that is too long for the Unix domain socket:
>     Temp dir: /var/spool/sge/wv2/tmp/<9 digit grid job id>.1.<16 character 
> queuename>.q/openmpi-sessions-43757@<12character machine name>_0/50671

Personally I find it quite unusual to have the scratch directory being located 
in /var. Often it's a plain /scratch.

Could a symbolic link help? I mean: create it in /tmp and point it to 
/var/spool/sge/wv2/tmp/<9 digit grid job id>.1.<16 character queuename>.q Then 
/tmp/$(mktemp -u XXXX) could be shorter which you define as TMPDIR before 
starting `mpiexec`.


If it happens only occasionally, maybe it depends on the length of the hostname 
where it's running on?

If the admin are nice, the could define a symbolic link directly as /scratch 
pointing to /var/spool/sge/wv2/tmp and setup in the queue configuration 
/scratch as being TMPDIR. Effect and location like now, but safes some 

-- Reuti
users mailing list

Reply via email to