Kakoli what version of the VOMS server are you running? I have seen that error message on a couple different voms servers and both times it has been that the server needed to be restarted (due to a bug that the VOMS server would crash if someone not in the VO tried to voms-proxy-init against it). Voms 1.8.3 and voms 1.8.8 both have bugs of that nature. It could be that the problem has nothing to do with gt 4.2. I have seen that error message several times with GT 4.0.7
Steve Timm On Mon, 8 Dec 2008, Jim Basney wrote:
See: http://www.globus.org/toolkit/docs/4.2/4.2.0/rn/release_notes.html#rn-changesummaries-security I suspect the VOMS server logs would have more information about the error. My guess is that the VOMS server does not accept RFC 3820 compliant proxy certificates, which are generated by default in GT 4.2. Try 'voms-proxy-init -proxyver 2'. Kakoli Sen wrote:Dear all, Is there any major difference between GSI layer of GT4.0.7 and GT4.2.0? The command voms-proxy-init(which calls grid-proxy-init internally) is giving error with GT4.2. Error: Could not establish authenticated connection with the server. globus_gss_assist token :3: read failure: Connection closed None of the contacted servers for test were capable of returning a valid AC for the user. Is there any way to get more information on the error? Regards, Kakoli Sen ________________________________________________________________________ KAKOLI SEN Ph:91-80-25341909/215(Extn. 309) C-DAC Knowledge Park E-mail: #1, Old Madras Road [EMAIL PROTECTED] Bangalore - 560 038, INDIA [EMAIL PROTECTED] ________________________________________________________________________
-- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 [EMAIL PROTECTED] http://home.fnal.gov/~timm/ Fermilab Computing Division, Scientific Computing Facilities, Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.
