Hi Zvi,
> The command to create the proxy was :
>
> voms-proxy-init --voms kzvo.isragrid.org.il --debug
OK, I wanted to see if e.g. you had been trying the "-rfc" option as well,
which could have led to errors similar to the ones you observed.
> And then the submit command :
>
> glite-wms-job-submit -e https://wms-ce.haifa.il.ibm.com:7443/glite_wms_wmproxy_server -a ex.jdl
>
> Or
>
> glite-wms-job-submit -e https://wms-ce.haifa.il.ibm.com:7443/glite_wms_wmproxy_server -r
> eladby-temp.haifa.il.ibm.com:8443/cream-pbs-kzvo -a ex.jdl
>
> This morning after renewing the proxy I tried the first glite-wms-job-submit option (not
> speciying the CE by -r) and got back the status :
> ======================= glite-wms-job-status Success =====================
> BOOKKEEPING INFORMATION:
>
> Status info for the Job : https://wms-ce.haifa.il.ibm.com:9000/d53KPcMRPKvA1unbSJLsyw
> Current Status: Waiting
> Status Reason: BrokerHelper: no compatible resources
> Submitted: Tue Jun 18 08:10:44 2013 IDT
> ==========================================================================
If you do not specify the CE destination on the command line,
you rely on the matchmaking to be done by the WMS:
https://wiki.egi.eu/wiki/Tools/Manuals/SiteProblemsFollowUp -->
https://wiki.egi.eu/wiki/Tools/Manuals/TS55
https://wiki.egi.eu/wiki/Tools/Manuals/TS53
> Then after 10 minutes I switched to the second submit to wms command (with the -r) and got the
> same error as below , namely:
>
> failed: FaultString=[SSL error] -
> > FaultCode=[SOAP-ENV:Client] - FaultSubCode=[SOAP-ENV:Client] - FaultDetail=
> > [SSL authentication failed in tcp_connect(): check password, key file, and ca file.]
>
>
> And now it repeats like this . The first submit option returns 'Waiting' .
> The second returns the SSL error
Apparently you managed to overcome that problem in the meantime:
it would be interesting to know what needed to be done!
> What is the cure though (whther they are tried in short succession or not ) ?
> Is there some log file at the wms where I can look for more indicative info
Check /var/log/wms/* and you probably need to increase the log level
of the Workload Manager in /etc/glite-wms/glite_wms.conf.
|