I have 2 of the system which i upgraded to 3.0 13 and on both of them i am getting the same . On Mon, Feb 23, 2009 at 4:14 PM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > Shekhar Gupta wrote: >> >> 2009/02/23 13:09:00| tunnelReadServer: FD 350: read failure: (0) Success >> 2009/02/23 13:28:36| tunnelReadServer: FD 332: read failure: (0) Success >> 2009/02/23 13:37:51| tunnelReadServer: FD 401: read failure: (0) Success >> 2009/02/23 13:38:38| tunnelReadServer: FD 395: read failure: (0) Success >> 2009/02/23 13:38:48| tunnelReadServer: FD 569: read failure: (0) Success >> 2009/02/23 13:39:42| tunnelReadServer: FD 425: read failure: (0) Success >> 2009/02/23 14:04:25| tunnelReadServer: FD 37: read failure: (0) Success >> 2009/02/23 14:21:09| tunnelReadServer: FD 542: read failure: (0) Success >> 2009/02/23 14:28:44| tunnelReadServer: FD 758: read failure: (0) Success >> 2009/02/23 14:29:30| tunnelReadServer: FD 713: read failure: (0) Success >> 2009/02/23 14:35:59| tunnelReadServer: FD 126: read failure: (0) Success >> 2009/02/23 14:37:52| tunnelReadServer: FD 356: read failure: (0) Success >> 2009/02/23 14:38:08| tunnelReadServer: FD 165: read failure: (0) Success >> 2009/02/23 14:40:36| tunnelReadServer: FD 543: read failure: (0) Success >> 2009/02/23 14:40:39| tunnelReadServer: FD 429: read failure: (0) Success >> 2009/02/23 14:40:47| tunnelReadServer: FD 396: read failure: (0) Success >> 2009/02/23 14:41:25| tunnelReadServer: FD 504: read failure: (32) Broken >> pipe >> 2009/02/23 14:42:43| tunnelReadServer: FD 383: read failure: (0) Success >> >> Can any one tell me what does this mean > > Might mean a read or write problem. might mean nothing. > We are looking for someone able to reproduce this message reliably and also > having the skills to track down why it displays in the occasions that squid > keeps going afterwards without an additional fatal error cropping up. > > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13 > Current Beta Squid 3.1.0.5 >
