It seems a wrong count or a lost race, it is checking too late and the
file and the /tmp/ompi.LAPTOP-82F08ILC.197609 tree is already close and gone
315 30730897 [main] orterun 93 close: close(21)
310 30731207 [main] orterun 93 fhandler_base::close: closing
'/tmp/ompi.LAPTOP-82F08ILC.197609' handle 0x4FC
321 30731528 [main] orterun 93 close: 0 = close(21)
711 30820954 [main] orterun 93 close: close(20)
543 30822098 [] orterun 93 fhandler_base::close: closing ':fifo'
handle 0x6D8
734 30823934 [main] orterun 93 fhandler_base::close: closing
'/tmp/ompi.LAPTOP-82F08ILC.197609/pid.93/0/debugger_attach_fifo' handle 0x0
555 30824489 [main] orterun 93 close: 0 = close(20)
573 30825062 [main] orterun 93 open:
open(/tmp/ompi.LAPTOP-82F08ILC.197609/pid.93/0/debugger_attach_fifo, 0x4000)
567 30837753 [main] orterun 93 fhandler_base::open:
(\??\D:\cygwin64T\tmp\ompi.LAPTOP-82F08ILC.197609\pid.93\0\debugger_attach_fifo,
0x10C000)
578 30839496 [main] orterun 93 fhandler_base::open: 0xC000003A =
NtCreateFile (0x3030303030675963, 0x80100000,
\??\D:\cygwin64T\tmp\ompi.LAPTOP-82F08ILC.197609\pid.93\0\debugger_attach_fifo,
io, NULL, 0x0, 0x7, 0x1, 0x4020, NULL, 0)
543 30840039 [main] orterun 93 fhandler_base::open: 0 =
fhandler_base::open(\??\D:\cygwin64T\tmp\ompi.LAPTOP-82F08ILC.197609\pid.93\0\debugger_attach_fifo,
0x10C000)
564 30841145 [main] orterun 93 open: -1 =
open(/tmp/ompi.LAPTOP-82F08ILC.197609/pid.93/0/debugger_attach_fifo,
0xC000), errno 2
Am 04.02.2020 um 04:17 schrieb Ralph Castain via devel:
It is the latter one it is complaining about:
/tmp/ompi.LAPTOP-82F08ILC.197609/pid.93/0/debugger_attach_fifo
I have no idea why it is complaining.
On Feb 3, 2020, at 2:03 PM, Marco Atzeri via devel <devel@lists.open-mpi.org>
wrote:
Am 03.02.2020 um 18:15 schrieb Ralph Castain via devel:
Hi Marco
mpirun isn't trying to run a debugger. It is opening a fifo pipe in case a
debugger later wishes to attach to the running job - it is used by an
MPIR-based debugger to let mpirun know that it is attaching. My guess is that
the code is attempting to create the fifo in an unacceptable place under Cygwin
- I forget the directory it is trying to use.
for what I see it write in two places
under /dev/shm where it leave some trace
$ ls -l /dev/shm/
total 33M
-rw------- 1 Marco Kein 4.1M Feb 3 22:01
vader_segment.LAPTOP-82F08ILC.45860001.0
-rw------- 1 Marco Kein 4.1M Feb 3 22:01
vader_segment.LAPTOP-82F08ILC.45860001.1
-rw------- 1 Marco Kein 4.1M Feb 3 22:01
vader_segment.LAPTOP-82F08ILC.45860001.2
-rw------- 1 Marco Kein 4.1M Feb 3 22:01
vader_segment.LAPTOP-82F08ILC.45860001.3
-rw------- 1 Marco Kein 4.1M Feb 3 22:02
vader_segment.LAPTOP-82F08ILC.45a60001.0
-rw------- 1 Marco Kein 4.1M Feb 3 22:02
vader_segment.LAPTOP-82F08ILC.45a60001.1
-rw------- 1 Marco Kein 4.1M Feb 3 22:02
vader_segment.LAPTOP-82F08ILC.45a60001.2
-rw------- 1 Marco Kein 4.1M Feb 3 22:02
vader_segment.LAPTOP-82F08ILC.45a60001.3
and under /tmp/ompi.LAPTOP-82F08ILC.197609
as /tmp/ompi.LAPTOP-82F08ILC.197609/pid.93/0/debugger_attach_fifo
where at the end nothing remain under /tmp
The only thing strange I see is some tentative access to /proc/elog
that does not exist in Cygwin
