 |
 |
Hi I hope it does not matter :) I just saw a very old bugzilla bug from EDG days that mentioned the same error; apparently this had to do with logging attempts made from a job whose proxy had expired. So maybe it does not matter for the RB but signals a real error for the user (proxy wasn't long enough). JT ps link in google cache http://72.14.207.104/search?q=cache:m1-Uyy-ira0J:marianne.in2p3.fr/datagrid/bugzilla/long_list.cgi%3Fbuglist%3D2213+edg-wl-bkserverd+SSL+hanshake+failed&hl=nl&client=firefox-a Wei Xing wrote: > Hi, Jeff, > > Thanks for your prompt reply. > > So do you mean it does not matter? Does it effect the Logging and > Booking server? Anything related Network Server? > > Regards > > Wei > > Jeff Templon wrote: > >> I think it's a secret competition. The WMS folks got jealous of the >> R-GMA folks. See, R-GMA used to print lots of failure messages when >> it was in fact working correctly, the WMS did not have this feature. >> As far as I can tell, the messages below are their attempt to catch up >> to R-GMA in this regard. >> >> Real answer: my RB has lots of these messages too, and it doesn't >> appear to make any difference, and I don't remember seeing any answer >> to this question. >> >> JT >> >> Wei Xing wrote: >> >>> Hi, >>> >>> There is error message appearing continually in my Resource Broker log: >>> >>> Oct 20 14:44:13 rb101 edg-wl-interlogd[4233]: queue_thread: >>> event_queue_connect: edg_wll_ssl_connect >>> Oct 20 14:45:13 rb101 edg-wl-bkserverd[11347]: SSL hanshake failed >>> >>> Any idear about it? >>> >>> Thx, >>> >>> Wei >>> >> > >