Re: [Evolution] I/O operation timing out

[Eric Beversluis <ebever researchintegration org>]

On Mon, 2013-10-28 at 11:00 -0400, Adam Tauno Williams wrote:
> On Mon, 2013-10-21 at 18:58 -0400, Eric Beversluis wrote:
> > I now have Evo 3.8.5 on Fedora 19. So everything's up to date in Kansas
> > City. The problem persists. I'm doing 'send/receive' on three accounts,
> > all the same domain, all hosted at omnis.com. I've done some traceroutes
> > and my impression is that most if not all of the jumps take longer when
> > the attempt times out. This presumably would mean that it's not a
> > problem at the omnis.com end. So I repeat my earlier query: Is there
> > some way to tell Evolution to wait longer before it times out? I've
> > already set net.ipv4.tcp_syn_retries to 7, which is supposed to give
> > about 90 seconds (per
> > http://www.sekuda.com/overriding_the_default_linux_kernel_20_second_tcp_socket_connect_timeout).
> > But I'm getting the timeout error after about 45 seconds and 60 seconds.
> > And it's still intermittent--sometimes stuff downloads right away;
> > sometimes only one or two accounts download and then it times out.
>
> Is this for an IMAP or POP account?
>
> If you run "CAMEL_VERBOSE_DEBUG=1 evolution" do you see anything about
> the timeout?  
>
> I'm not an expert but noodling around in the camel code in EDS I do not
> see anything that looks like a socket timeout; so I'd guess whatever the
> default is what the default is.
Evolution experts/developers out there: Is there anything in Evolution
code that creates a time out? Where is the error message that the I/O
operation timed out coming from?