Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: [OMPI users] Permission denied, please try again.
From: Syed Ahsan Ali (ahsanshah01_at_[hidden])
Date: 2012-08-01 03:45:17


Dear All

I am having problem while running an application on cluster. The
application was working fine but now this error has arised . we used to run
the application the same way with user pmdtest and there was no error. I
dont know which permission it is asking for. Please help!

 [pmdtest_at_pmd02 d00_dayfiles]$ less *_hrm
mpirun -np 32 /home/MET/hrm/bin/hrm
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,gssapi-with-mic,password).
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,gssapi-with-mic,password).
--------------------------------------------------------------------------
A daemon (pid 25164) died unexpectedly with status 255 while attempting
to launch so we are aborting.

There may be more information reported by the environment (see above).

This may be because the daemon was unable to find all the needed shared
libraries on the remote node. You may set your LD_LIBRARY_PATH to have the
location of the shared libraries on the remote nodes and this will
automatically be forwarded to the remote nodes.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun noticed that the job aborted, but has no info as to the process
that caused that situation.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun was unable to cleanly terminate the daemons on the nodes shown
below. Additional manual cleanup may be required - please refer to
the "orte-clean" tool for assistance.
--------------------------------------------------------------------------
        compute-02-02 - daemon did not report back when launched
        compute-02-00 - daemon did not report back when launched
        compute-02-03 - daemon did not report back when launched

Best Regards
Ahsan