Ask a questionAsk a question
 

Answermpiexec -tracefile option does not work on cluster?

  • Tuesday, June 30, 2009 7:22 PMtosa.yasunari Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I thought that it is a good idea to try "mpiexec -tracefile mytrace.etl MPIApp.exe".    I get the error:
    Aborting: failed to start tracing on CNODE00
    Error(183) Cannot create a file when that file already exists.

    I have no problem running "mpiexec MPIApp.exe".  

    Can you tell me how I can get the trace file? 

    Thank you.

Answers

  • Monday, July 06, 2009 5:01 PMLioMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi,

    One posability is that the tracing session is still on from a failed (Ctrl-C) run or a cancelled job; hence the new run can not create that session again.

    Run "logman stop msmpi -ets" and then retry tracing.

    .Erez

All Replies

  • Friday, July 03, 2009 7:12 AMJohannes_de Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

    there might be an issue with the access permissions.
    What working directory did you set? Have you write /create permissions there?
    Otherwise the trace file might be written to one default location for all users and you might not have sufficient rights to overwrite the trace files of other users.

    Johannes
    JH
  • Monday, July 06, 2009 5:01 PMLioMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi,

    One posability is that the tracing session is still on from a failed (Ctrl-C) run or a cancelled job; hence the new run can not create that session again.

    Run "logman stop msmpi -ets" and then retry tracing.

    .Erez