 |
 |
Hi Frabrizio, It seems there is a problem with sicket management foir Linux. Would it be possible to at least print what the eror was when it happens (as opped to just saying "error"). Turning on debugging is not an option since this problem occurs once in every 100 runs or so and the log files would get too big. In general it is always use ful to print the reason for teh error no matter what so that you don't have to ask the user to rerun the job with debigging. Andy ----- Original Message ----- From: "Bill Weeks" <[log in to unmask]> To: <[log in to unmask]> Sent: Monday, February 28, 2005 10:36 AM Subject: xroot client error messages > Hi, > Here is a sample of the read errors running xrdtest on a linux client > connecting to a linux server, e.g. noma0xxx -> don0001: > > 050225 11:26:19 000 Xrd: XrdClientMessage::ReadRaw Error reading 1 bytes. > 050225 11:26:20 001 Xrd: ReadPartialAnswer Error reading msg from connmgr > (server [134.79.190.11:1094]). > 050225 11:26:20 001 Xrd: HandleServerError No Load Balancer to contact after a > communication error with server [134.79.190.11:1094]. Rebouncing here. > 050225 11:27:21 000 Xrd: XrdClientMessage::ReadRaw Error reading 1 bytes. > 050225 11:27:22 001 Xrd: ReadPartialAnswer Error reading msg from connmgr > (server [134.79.190.11:1094]). > 050225 11:27:22 001 Xrd: HandleServerError No Load Balancer to contact after a > communication error with server [134.79.190.11:1094]. Rebouncing here. > 050225 11:27:22 000 Xrd: XrdClientMessage::ReadRaw Error reading 1 bytes. > 050225 11:29:22 001 Xrd: ReadPartialAnswer Error reading msg from connmgr > (server [134.79.190.11:1094]). > 050225 11:29:22 001 Xrd: HandleServerError No Load Balancer to contact after a > communication error with server [134.79.190.11:1094]. Rebouncing here. > 050225 11:30:23 000 Xrd: XrdClientMessage::ReadRaw Error reading 1 bytes. > 050225 11:30:24 001 Xrd: ReadPartialAnswer Error reading msg from connmgr > (server [134.79.190.11:1094]). > 050225 11:30:24 001 Xrd: HandleServerError No Load Balancer to contact after a > communication error with server [134.79.190.11:1094]. Rebouncing here. > 050225 11:30:24 000 Xrd: XrdClientMessage::ReadRaw Error reading 1 bytes. > 050225 11:32:24 001 Xrd: ReadPartialAnswer Error reading msg from connmgr > (server [134.79.190.11:1094]). > 050225 11:32:24 001 Xrd: HandleServerError No Load Balancer to contact after a > communication error with server [134.79.190.11:1094]. Rebouncing here. > 050225 11:32:24 000 Xrd: XrdClientMessage::ReadRaw Error reading 1 bytes. > 050225 11:34:24 001 Xrd: ReadPartialAnswer Error reading msg from connmgr > (server [134.79.190.11:1094]). > 050225 11:34:24 001 Xrd: HandleServerError No Load Balancer to contact after a > communication error with server [134.79.190.11:1094]. Rebouncing here. > 10:46:56 root://don0001.slac.stanford.edu:1094//u1/junk1 Starting to read > 11:34:24 root://don0001.slac.stanford.edu:1094//u1/junk1 n=500000, nb=500000, > ET=2848.20, 0.2 Kb/sec latency 5695 143 120010347 > > >