On Sep 17, 2007, at 11:26 PM, Jelena Pjesivac-Grbovic wrote:
I am trying to set up mtt client for collectives on UTK clusters and I
received the following error
---
./client/mtt --scratch /home/pjesa/mtt/scratch/ \
--file /home/pjesa/mtt/collective-bakeoff/samples/ompi-core-
perf-testing.ini \
--verbose --print-time
*** MTT: ./client/mtt --scratch /home/pjesa/mtt/scratch/ --file
/home/pjesa/mtt/collective-bakeoff/samples/ompi-core-perf-
testing.ini
--verbose --print-time
*** WARNING: Unable to read hostfile: /home/pjesa/machinefile --
ignoring
Note this error as well -- make sure that this hostfile exists. If
you're running under Torque, you probably don't need a hostfile (I'm
not sure how well we've tested under Torque, but it won't be hard to
fix if there's a problem).
*** Reporter initializing
Initializing reporter module: MTTDatabase
Set HTTP credentials for realm "OMPI"
*** WARNING: >> Failed test ping to MTTDatabase URL:
https://www.open-mpi.org:443/mtt/submit/
*** WARNING: >> Error was: 501 Protocol scheme 'https' is not
supported
(Crypt::SSLeay not installed)
LWP will support https URLs if the Crypt::SSLeay module is
installed.
More information at <http://www.linpro.no/lwp/libwww-perl/
README.SSL>.
*** ERROR: Module aborted: MTT::Reporter::MTTDatabase:Init: ***
ERROR: >>
Do not want to continue with possible bad submission URL --
aborting
It's not that MTT itself requires SSL, it's that the OMPI test
results submission URL https because a password is sent.
Sorry. :-(
--
Jeff Squyres
Cisco Systems
