Re: read(2) and ETIMEDOUT

2001-06-10 Thread Valentin Nechayev
Thu, Jun 07, 2001 at 20:18:46, gbarr (Graham Barr) wrote about Re: read(2) and ETIMEDOUT: I'm quite sure ETIMEDOUT is a result of hitting the setsockopt SO_RCVTIMEO value when doing a read. I had been thinking along those lines too. But immediately before calling read, select said

Re: read(2) and ETIMEDOUT

2001-06-08 Thread Terry Lambert
Ian Dowse wrote: In message [EMAIL PROTECTED], Graham Barr writes: Also why does this happen only every few hours ? There is a lot of data going through these connections maybe the timer for SO_RCVTIMEO is not being reset. But then we have another server, with a similar number of

Re: read(2) and ETIMEDOUT

2001-06-08 Thread Bernd Walter
On Thu, Jun 07, 2001 at 03:20:58PM -0700, Matt Dillon wrote: : :On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote: : : : : :Thanks, I will try setting errno, but I don't think it is signals. : :I have been running truss on the process. The relevant part is : : :

Re: read(2) and ETIMEDOUT

2001-06-08 Thread Graham Barr
On Fri, Jun 08, 2001 at 09:39:15PM +0200, Bernd Walter wrote: On Thu, Jun 07, 2001 at 03:20:58PM -0700, Matt Dillon wrote: : :On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote: : : : : :Thanks, I will try setting errno, but I don't think it is signals. : :I have been

read(2) and ETIMEDOUT

2001-06-07 Thread Graham Barr
A while ago our systems were upgraded from 4.2 to 4.3-RC, and at this time we started seeing problems that I am having a difficult time tracking down. We have a server process which is connected to by many other machines, each of them streams data in via tcp/ip. These connections are pretty much

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Matt Dillon
:A while ago our systems were upgraded from 4.2 to 4.3-RC, and at :this time we started seeing problems that I am having a difficult :time tracking down. : :We have a server process which is connected to by many other :machines, each of them streams data in via tcp/ip. These connections :are

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Graham Barr
Thanks, I will try setting errno, but I don't think it is signals. I have been running truss on the process. The relevant part is gettimeofday(0xbfbffa54,0x0) = 0 (0x0) select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74)= 3 (0x3) read(0x16,0xa2da000,0x8000)

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Matt Dillon
: :Thanks, I will try setting errno, but I don't think it is signals. :I have been running truss on the process. The relevant part is : :gettimeofday(0xbfbffa54,0x0) = 0 (0x0) :select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74)= 3 (0x3) :read(0x16,0xa2da000,0x8000)

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Graham Barr
On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote: : :Thanks, I will try setting errno, but I don't think it is signals. :I have been running truss on the process. The relevant part is : :gettimeofday(0xbfbffa54,0x0) = 0 (0x0)

Re: read(2) and ETIMEDOUT

2001-06-07 Thread rick norman
I've seen this behavior in the past. My impression is that it is load related. If you do a grep on ETIMEDOUT in /usr/src/sys/netinet, you will see where the tcp stack may return this message. There may be some sysctl params relating to timers that you can muck with. Rick Graham Barr wrote:

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Alfred Perlstein
* Graham Barr [EMAIL PROTECTED] [010607 12:17] wrote: Since people seem to be helping you in other ways, I'll just answer this one: So, here is my question. Does anyone know under what circumstance ETIMEDOUT may be returned from read(2) or is this a potential bug somewhere ? I'm quite sure

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Graham Barr
On Thu, Jun 07, 2001 at 03:09:17PM -0400, Alfred Perlstein wrote: * Graham Barr [EMAIL PROTECTED] [010607 12:17] wrote: Since people seem to be helping you in other ways, I'll just answer this one: So, here is my question. Does anyone know under what circumstance ETIMEDOUT may be

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Ian Dowse
In message [EMAIL PROTECTED], Graham Barr writes: Also why does this happen only every few hours ? There is a lot of data going through these connections maybe the timer for SO_RCVTIMEO is not being reset. But then we have another server, with a similar number of clients and data through put,

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Graham Barr
While this does sound very plausable,... The server does not do any writes, data only travels from the clients to the server. The clients and the server are connected to the same switch. The other server which is similar is on the same network and is connected to by the same machines as

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Matt Dillon
: :On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote: : : : : :Thanks, I will try setting errno, but I don't think it is signals. : :I have been running truss on the process. The relevant part is : : : :gettimeofday(0xbfbffa54,0x0) = 0 (0x0) :