That's not an error message. The warning is from the gatekeeper setup
telling you that you don't have a hostcert right now so it won't
publish your host's subject name. The other warning is telling you
you don't have MPI setup, so it won't auto-setup the MPI jobtype.
If you're not using GRAM2, it doesn't matter. If you're using GRAM2
but not MDS2, it doesn't matter.
Charles
On Oct 27, 2008, at 11:40 AM, Jan Muhammad wrote:
Hi All,
I had previously configured/build GT 4.2.0 and globus-container
worked fine. But that was not compatible with a service
(HelloWorld)running on another machine protected with PERMIS;
ultimately had to switch back to GT4.0.4 making sure that both
systems have same GT4 versions.
Now having a typical certificates related error. Thinking that might
any one of you have encountered such errors in the past.
Can you please suggest me either I need to re-configure certificates
for GT4.0.4? As these were configured for GT4.2.0? Or it doesn't
matter? I'm bit confused about the certificates issue. Although the
file "usercert.pem" & "userkey.pem" both exist which I configured
while building GT4.2.0.
Error Message is as follows:
---------------------------------------------------------------------
Reading gatekeeper configuration file...
Warning: Host cert file: /etc/grid-security/hostcert.pem not found.
Re-run
setup-globus-gram-job-manager after installing host cert
file.
Determining system information...
Creating job manager configuration file...
Done
..Done
running /usr/local/globus-4.0.4/setup/globus/setup-globus-job-
manager-fork..[ Changing to /usr/local/globus-4.0.4/setup/globus ]
find-fork-tools: WARNING: "Cannot locate mpiexec"
find-fork-tools: WARNING: "Cannot locate mpirun"
checking for mpiexec... no
checking for mpirun... no
find-fork-tools: creating ./config.status
config.status: creating fork.pm
..Done
-------------------------------------------------------------------------------------
Regards
________________________
Jan Muhammad