Re: [Evolution] I/O operation timing out

[Adam Tauno Williams]

On Fri, 2014-01-24 at 23:28 +, Patrick O'Callaghan wrote:
> On 24 January 2014 22:22, Pete Biggs  wrote:
> > To be honest it sounds like something is wrong with your NAT
> > router/firewall in that the packets are being sent to the wrong host -
> > it could be configuration or it could just be a bug, but it certainly
> > seems like packets are going astray.
> I would agree. The router may not be handling NAT correctly or may be
> limiting the number of internal machines it supports. As a first step,
> try resetting it to see what happens.

Or the ISP is doing NAT `for you` and their NAT is oversubscribed or
saturated.  In which case you are screwed.  This smells a lot like a
network issue that just, as-far-as-we-know, manifests [at least] for
this specific use.

Can you establish a VPN tunnel to somewhere else, make that your default
route, and see if doing all the downloads over that solves the problem?

-- 
Adam Tauno Williams  GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Eric Beversluis]

On Fri, 2014-01-24 at 23:28 +, Patrick O'Callaghan wrote:
> On 24 January 2014 22:22, Pete Biggs  wrote:
> > To be honest it sounds like something is wrong with your NAT
> > router/firewall in that the packets are being sent to the wrong host -
> > it could be configuration or it could just be a bug, but it certainly
> > seems like packets are going astray.
> 
> I would agree. The router may not be handling NAT correctly or may be
> limiting the number of internal machines it supports. As a first step,
> try resetting it to see what happens.
> 
> poc

I took my problem to the Genius Bar at Apple, but without any help. The
genius didn't know what Fedora is and even though we could clearly see
that turning on Mac Mail was causing the Evo I/O timeout (at least
intermittently), he claimed that since there didn't seem to be any
problem with the Mac he couldn't do anything.He also kept saying it was
probably a problem with my POP accounts

I'll try resetting the wireless router and also get a newer modem
(especially since somewhere TimeWarner started charging me $5 or more
per month modem rental for an old 5101...).

"but it certainly seems like packets are going astray." How would
anything that Airport or Mac Mail does cause packets to go astray? It
seems like somehow Mac Mail is continuously sending and thus clogging
the mail-receiving ports (995).

Thanks

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Eric Beversluis]

On Sat, 2014-01-25 at 19:19 +, Patrick O'Callaghan wrote:
> On Sat, 2014-01-25 at 11:36 -0500, Eric Beversluis wrote:
> > "but it certainly seems like packets are going astray." How would
> > anything that Airport or Mac Mail does cause packets to go astray? It
> > seems like somehow Mac Mail is continuously sending and thus clogging
> > the mail-receiving ports (995).
> 
> That doesn't make a lot of sense. I presume we're talking about 2
> different client machines (seems logical since one is Fedora and the
> other a Mac, unless Fedora is running on a VM). So how could one of them
> clog the POP *download* port of the other, which isn't even directly
> connected to it? Unless the Mac is running some kind of DOS bot. Do you
> see any other network effects? Are ping times from the Fedora machine to
> the mail server affected when the Mac is on?
 They seem to be a bit slower, but there's enough variability among the
replies that it's hard to tell. I see an occasional 1000ms when the Mac
is on, but when it's off I see some mid-3figure ms times. So that's hard
to judge.

> 
> Also, looking back I see you're using Fedora 17. F17 went EOL about a
> year ago, so I'd recommend updating to F20 before proceeding. You'll at

This was at the beginning of the thread. I since upgraded to F19 but the
problem continued.

> least get a newer version of Evo and the problem might go away.
> 
> Finally, are you the OP for this thread? You seem to be using two
> different mail accounts.

Yeah--for some reason I started this account using the one address and
unfortunately forget to stick with that one.

> 
I got a nice off-list reply from Pete Biggs that's helping me understand
how packets returning from mail.researchintegration.org might be getting
misdirected. Seems maybe my router may be having trouble identifying
which packets from my mail server should go to which host. Which seems
strange, since surely different hosts on a NAT'd LAN communicate with
the same remote mail server all the time, don't they? So I think my next
step is upgrading my router--I have a "new" one, but it's apparently not
a recent model (Netgear WPN824N).

Thanks.

> poc
> 
> poc
> 


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Carpetnailz]

On Sat, 2014-01-25 at 19:19 +, Patrick O'Callaghan wrote:
> On Sat, 2014-01-25 at 11:36 -0500, Eric Beversluis wrote:
> > "but it certainly seems like packets are going astray." How would
> > anything that Airport or Mac Mail does cause packets to go astray? It
> > seems like somehow Mac Mail is continuously sending and thus clogging
> > the mail-receiving ports (995).
> 
> That doesn't make a lot of sense. I presume we're talking about 2
> different client machines (seems logical since one is Fedora and the
> other a Mac, unless Fedora is running on a VM). So how could one of them
> clog the POP *download* port of the other, which isn't even directly
> connected to it? Unless the Mac is running some kind of DOS bot. Do you
> see any other network effects? Are ping times from the Fedora machine to
> the mail server affected when the Mac is on?
> 
> Also, looking back I see you're using Fedora 17. F17 went EOL about a
> year ago, so I'd recommend updating to F20 before proceeding. You'll at
> least get a newer version of Evo and the problem might go away.

THat was at the start of the thread. Early on I upgraded to F19, but the
problems persisted.

> 
> Finally, are you the OP for this thread? You seem to be using two
> different mail accounts.
> 
> poc
> 
> poc
> 
Well I've rebooted the wirelss router and now things seem for the moment
to be going OK. But I've tried that in the past and either they didn't
fix or the problem soon reappeared after a certain amount of activity.

If it reappears I think I'll just update and upgrade my wireless
router. 

Thanks to all and hopefully this thread is finished.

EB

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Patrick O'Callaghan]

On Sat, 2014-01-25 at 11:36 -0500, Eric Beversluis wrote:
> "but it certainly seems like packets are going astray." How would
> anything that Airport or Mac Mail does cause packets to go astray? It
> seems like somehow Mac Mail is continuously sending and thus clogging
> the mail-receiving ports (995).

That doesn't make a lot of sense. I presume we're talking about 2
different client machines (seems logical since one is Fedora and the
other a Mac, unless Fedora is running on a VM). So how could one of them
clog the POP *download* port of the other, which isn't even directly
connected to it? Unless the Mac is running some kind of DOS bot. Do you
see any other network effects? Are ping times from the Fedora machine to
the mail server affected when the Mac is on?

Also, looking back I see you're using Fedora 17. F17 went EOL about a
year ago, so I'd recommend updating to F20 before proceeding. You'll at
least get a newer version of Evo and the problem might go away.

Finally, are you the OP for this thread? You seem to be using two
different mail accounts.

poc

poc

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[James Lay]

On Fri, 2014-01-24 at 17:37 -0500, Eric Beversluis wrote:

> On Fri, 2014-01-24 at 22:22 +, Pete Biggs wrote:
> > > Update: I had pretty much decided the problem (getting I/O timeout with
> > > Send/Receive on Evolution--doesn't seem to affect sending new email) lay
> > > in my Motorola 5101 modem from TimeWarner. It may still lie there but I
> > > just noticed this: My wife is out of town for a week. She uses a Mac and
> > > Mac's Mail, which is on all the time. With her gone, I haven't had any
> > > problems with my Evolution mail failing to connect ("Error while
> > > fetching mail from  Could not connect to  I/O operation timed
> > > out"). So I pulled out an old MacBook and sure enough, as soon as I
> > > turned on Mail, I started getting the timeout problems again. Turn off
> > > Mail and Evolution mail works fine. 
> > 
> > That'll be interesting to sort out!
> > 
> > Are you (both) on wired or wireless connections? 
> The apple--both my wife's and the one I'm testing today--are on
> wireless. The Fedora 19 box is mostly on wireless, but the problem seems
> to exist also when I switch to an Ethernet connection.
> 
> > 
> > Are you both using the same server / account for mail?
> > 
> > To be honest it sounds like something is wrong with your NAT
> > router/firewall in that the packets are being sent to the wrong host -
> > it could be configuration or it could just be a bug, but it certainly
> > seems like packets are going astray.
> Using a brand new Netgear RangeMax N150 WPN 824N wireless router. I
> ditched my old one because I thought it might be the problem.
> 
> > 
> > > 
> > > Interestingly this does not happen on this computer at work, in a small
> > > office where the boss uses Mac and Mac Mail all the time--even when he
> > > was using earlier versions of Mac.
> > 
> > It's probably because your office doesn't use a NAT'd network - or that
> > the NAT router works properly.
> > 
> Yes--we're Nat'd there too.
> 
> > P.
> > 
> > 
> > ___
> > evolution-list mailing list
> > evolution-list@gnome.org
> > To change your list options or unsubscribe, visit ...
> > https://mail.gnome.org/mailman/listinfo/evolution-list
> 
> 
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list


Packet capture it...it's a linux box after all ;)  Guessing, for some
odd reason port saturation is happening for whatever reason.  Look for
icmp replies from the router for clues.

James
<>

signature.asc
Description: This is a digitally signed message part
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Eric Beversluis]

On Fri, 2014-01-24 at 22:22 +, Pete Biggs wrote:
> > Update: I had pretty much decided the problem (getting I/O timeout with
> > Send/Receive on Evolution--doesn't seem to affect sending new email) lay
> > in my Motorola 5101 modem from TimeWarner. It may still lie there but I
> > just noticed this: My wife is out of town for a week. She uses a Mac and
> > Mac's Mail, which is on all the time. With her gone, I haven't had any
> > problems with my Evolution mail failing to connect ("Error while
> > fetching mail from  Could not connect to  I/O operation timed
> > out"). So I pulled out an old MacBook and sure enough, as soon as I
> > turned on Mail, I started getting the timeout problems again. Turn off
> > Mail and Evolution mail works fine. 
> 
> That'll be interesting to sort out!
> 
> Are you (both) on wired or wireless connections? 
The apple--both my wife's and the one I'm testing today--are on
wireless. The Fedora 19 box is mostly on wireless, but the problem seems
to exist also when I switch to an Ethernet connection.

> 
> Are you both using the same server / account for mail?
> 
> To be honest it sounds like something is wrong with your NAT
> router/firewall in that the packets are being sent to the wrong host -
> it could be configuration or it could just be a bug, but it certainly
> seems like packets are going astray.
Using a brand new Netgear RangeMax N150 WPN 824N wireless router. I
ditched my old one because I thought it might be the problem.

> 
> > 
> > Interestingly this does not happen on this computer at work, in a small
> > office where the boss uses Mac and Mac Mail all the time--even when he
> > was using earlier versions of Mac.
> 
> It's probably because your office doesn't use a NAT'd network - or that
> the NAT router works properly.
> 
Yes--we're Nat'd there too.

> P.
> 
> 
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Patrick O'Callaghan]

On 24 January 2014 22:22, Pete Biggs  wrote:
> To be honest it sounds like something is wrong with your NAT
> router/firewall in that the packets are being sent to the wrong host -
> it could be configuration or it could just be a bug, but it certainly
> seems like packets are going astray.

I would agree. The router may not be handling NAT correctly or may be
limiting the number of internal machines it supports. As a first step,
try resetting it to see what happens.

poc
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Pete Biggs]

> Update: I had pretty much decided the problem (getting I/O timeout with
> Send/Receive on Evolution--doesn't seem to affect sending new email) lay
> in my Motorola 5101 modem from TimeWarner. It may still lie there but I
> just noticed this: My wife is out of town for a week. She uses a Mac and
> Mac's Mail, which is on all the time. With her gone, I haven't had any
> problems with my Evolution mail failing to connect ("Error while
> fetching mail from  Could not connect to  I/O operation timed
> out"). So I pulled out an old MacBook and sure enough, as soon as I
> turned on Mail, I started getting the timeout problems again. Turn off
> Mail and Evolution mail works fine. 

That'll be interesting to sort out!

Are you (both) on wired or wireless connections? 

Are you both using the same server / account for mail?

To be honest it sounds like something is wrong with your NAT
router/firewall in that the packets are being sent to the wrong host -
it could be configuration or it could just be a bug, but it certainly
seems like packets are going astray.

> 
> Interestingly this does not happen on this computer at work, in a small
> office where the boss uses Mac and Mac Mail all the time--even when he
> was using earlier versions of Mac.

It's probably because your office doesn't use a NAT'd network - or that
the NAT router works properly.

P.


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Carpetnailz]

On Thu, 2013-10-10 at 21:56 -0400, Carpetnailz wrote:
> I'm running Evo 3.4.4 on Fedora 17. 
> 
> About half the time or so when I do Send/Receive, I get this error
> message:
> 
> Error while Fetching Mail.
> Could not connect to mail.researchintegration.org: I/O operation timed
> out.
> 
> Sometimes one or two of the three accounts I'm connected to there
> download before the error occurs, sometimes none. About half the time it
> works OK.
> 
> The host of my domain says they've checked and their system is ok. Also,
> my wife, using Mac Mail, doesn't have these problems. And the problems
> occur for me at work as well as at home. My other internet connections
> do not seem problematic.
> 
> I tried switching from tls to no encryption, but that did not help.
> 
> Thanks.
> 
> 
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list

Update: I had pretty much decided the problem (getting I/O timeout with
Send/Receive on Evolution--doesn't seem to affect sending new email) lay
in my Motorola 5101 modem from TimeWarner. It may still lie there but I
just noticed this: My wife is out of town for a week. She uses a Mac and
Mac's Mail, which is on all the time. With her gone, I haven't had any
problems with my Evolution mail failing to connect ("Error while
fetching mail from  Could not connect to  I/O operation timed
out"). So I pulled out an old MacBook and sure enough, as soon as I
turned on Mail, I started getting the timeout problems again. Turn off
Mail and Evolution mail works fine. 

Interestingly this does not happen on this computer at work, in a small
office where the boss uses Mac and Mac Mail all the time--even when he
was using earlier versions of Mac.





___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Robert Seward]

Fedora 18. Evo 3.6.2 

I get timeouts on some accounts (usually gmail) about once a month or
so. The timeouts will persist for a day or two and then things will
return to normal (no timeouts at all). 

I have a single Internet connection, a Charter cable connection.

Sometimes during these time outs. The Gmail web interface will have
problems accessing my inbox as well. So in my case I am willing to
believe it might be internal Google problems.

Thanks,
Rob

On Mon, 2013-12-02 at 10:52 +, Patrick O'Callaghan wrote:
> 
> On 2 December 2013 00:51, samarjit Adhikari
>  wrote:
> I was facing similar issues of evolution timeout. My Evolution
> version was 3.10.2 from git source. Even I have observe that
> evolution was throwing timeout very intermittently. Thus I
> have decided to investigate it further. I could find that eds
> has implemented a "camel-network-service" which is responsible
> for connecting any network socket and identifying network
> change, calls "g_network_monitor_can_reach_async" with
> callback of "network_service_can_reach_cb". The call
> "g_network_monitor_can_reach_async" supposed to connect mail
> server and transfer the handle to Evolution to use. It was a
> gio call and my gio version is 2.38.1. Evolution was very
> dependent on this call and will misbehave if such call
> "g_network_monitor_can_reach_async" misbehaves. I have
> observed that the above mentioned call some time returns
> without actually connecting to the mail server(verified
> through wireshark) and in that case Evolution failed to
> connect showing "Timeout". Further looking into the code of
> gio implementation I could find that gio keep caching all
> network connections e.g. first time if evolution able to
> connect the mail server, gio will cache it and if you reopen
> evolution the call "g_network_monitor_can_reach_async" will
> return some time without connecting the mail server explicitly
> and such behavior continues till cache become invalid. 
> 
> 
> It is very annoying and could be a bug of GIO module rather
> than Evolution stack.
> I did not investigate further in GIO side due to time crunch ,
> but I believe it would certainly help in isolating evolution
> behavior from GIO.
> 
> 
> 
> 
> If there is a bug in GIO it should be reported to Bugzilla. If you
> aren't sure, report it to the Evo Bugzilla page and someone may bump
> it upstream.
> 
> 
> poc
> 
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list

-- 
Rob Seward
Bluestone Consulting Group, LLC

web: http://www.bluestone-consulting.com/
e-mail:  rsew...@bluestone-consulting.com
office:   734.726.0313



___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Patrick O'Callaghan]

On 2 December 2013 00:51, samarjit Adhikari wrote:

> I was facing similar issues of evolution timeout. My Evolution version was
> 3.10.2 from git source. Even I have observe that evolution was throwing
> timeout very intermittently. Thus I have decided to investigate it further.
> I could find that eds has implemented a "camel-network-service" which is
> responsible for connecting any network socket and identifying network
> change, calls "g_network_monitor_can_reach_async" with callback of
> "network_service_can_reach_cb". The call
> "g_network_monitor_can_reach_async" supposed to connect mail server and
> transfer the handle to Evolution to use. It was a gio call and my gio
> version is 2.38.1. Evolution was very dependent on this call and will
> misbehave if such call "g_network_monitor_can_reach_async" misbehaves. I
> have observed that the above mentioned call some time returns without
> actually connecting to the mail server(verified through wireshark) and in
> that case Evolution failed to connect showing "Timeout". Further looking
> into the code of gio implementation I could find that gio keep caching all
> network connections e.g. first time if evolution able to connect the mail
> server, gio will cache it and if you reopen evolution the call
> "g_network_monitor_can_reach_async" will return some time without
> connecting the mail server explicitly and such behavior continues till
> cache become invalid.
>
> It is very annoying and could be a bug of GIO module rather than Evolution
> stack.
> I did not investigate further in GIO side due to time crunch , but I
> believe it would certainly help in isolating evolution behavior from GIO.
>


If there is a bug in GIO it should be reported to Bugzilla. If you aren't
sure, report it to the Evo Bugzilla page and someone may bump it upstream.

poc
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Eric Beversluis]

On Sun, 2013-12-01 at 18:42 +, Pete Biggs wrote:
> > > 
> > > Almost certainly from your network stack; and my $$$ would be on your
> > > ISP/customer router.
> > > 
> > So it's this way?
> > -the router (Linksys WRT350N) is creating the time out (or something
> > else in the "subsystem")
> > -it aborts the mission and somehow signals Evolution, which then pops up
> > the timed out message
> 
> Sort of.  Your computer will send out ethernet packets to the internet
> via the router.  The packets that it sends out originate in Evolution
> via system calls.  Evolution doesn't create the packets, somewhere
> further down the ethernet software stack does that, evolution just tells
> the operating system what to put in the packets.
> 
> Once a packet is sent out, the system sits and waits for a response (as
> instructed by Evolution), if there is no response received in a specific
> time, then the operation times out.  The reasons that no packet has been
> received back are numerous - the remote end may be down, there may be a
> network problem, or some hardware may be malfunctioning.  There is no
> way to say for sure without extensive logging and tracing at both ends.
> 
> Once the network operation has timed out, the OS tells the originating
> program, i.e. Evolution, what has happened, and it is up to the program
> what it does then; Evolution happens to pop up a message about it,
> others may silently try again a number of times.  The timeout on the
> network operation is, I think, set by the OS, not the application.
> 
> The bottom line is that the timeout is NOT Evolution failing, it is
> merely reporting a failure elsewhere in the system.
> 
> P.
Thanks. That helps. I've decided there's something funky with that
particular wireless router's wireless that's causing the problem. I've
now got a different non-wireless router installed; everything works fine
when I go directly through it via Ethernet cable; I'm just using the
wireless part of the WRT350N as an AP; I'm getting the same problems as
soon as I go through it. And I don't seem to have the problems going
through other wireless systems.

Thanks to all.

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Bart Hollis]

On Sun, 2013-12-01 at 18:42 +, Pete Biggs wrote:>

> The bottom line is that the timeout is NOT Evolution failing, it is
> merely reporting a failure elsewhere in the system.

On my system, I have 12 email accounts.  All are POP.  I have both a DSL
connection through the phone company, and a cable connection through the
local cable company.  I have separate modems and use the same router,
changing only one setting and of course the cable between the router and
the modem.

When I use the DSL connection, all accounts work as expected.  When I
use the cable connection, I get timeout errors on seemingly random
accounts.  Different accounts each time I do a send/receive.

Therefore:  it is NOT evolution causing the problem, nor is it my
router.  It is something in the cable company's system causing the
problem.

I hope you have better luck getting a response from your carrier than I
have had.

Bart

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Eric Beversluis]

Interesting because now I'm getting the timeouts on my straight Ethernet
cable connection as well as through the wireless AP.

On Mon, 2013-12-02 at 06:21 +0530, samarjit Adhikari wrote:
> Hi All,
> 
> 
> I was facing similar issues of evolution timeout. My Evolution version
> was 3.10.2 from git source. Even I have observe that evolution was
> throwing timeout very intermittently. Thus I have decided to
> investigate it further. I could find that eds has implemented a
> "camel-network-service" which is responsible for connecting any
> network socket and identifying network change, calls
> "g_network_monitor_can_reach_async" with callback of
> "network_service_can_reach_cb". The call
> "g_network_monitor_can_reach_async" supposed to connect mail server
> and transfer the handle to Evolution to use. It was a gio call and my
> gio version is 2.38.1. Evolution was very dependent on this call and
> will misbehave if such call "g_network_monitor_can_reach_async"
> misbehaves. I have observed that the above mentioned call some time
> returns without actually connecting to the mail server(verified
> through wireshark) and in that case Evolution failed to connect
> showing "Timeout". Further looking into the code of gio implementation
> I could find that gio keep caching all network connections e.g. first
> time if evolution able to connect the mail server, gio will cache it
> and if you reopen evolution the call
> "g_network_monitor_can_reach_async" will return some time without
> connecting the mail server explicitly and such behavior continues till
> cache become invalid. 
> 
> 
> It is very annoying and could be a bug of GIO module rather than
> Evolution stack.
> I did not investigate further in GIO side due to time crunch , but I
> believe it would certainly help in isolating evolution behavior from
> GIO.
> 
> 
> With regards,
> Samarjit
> 
> 
> With regards,
> Samarjit
> 
> 
> On Mon, Dec 2, 2013 at 12:12 AM, Pete Biggs  wrote:
> 
> > >
> > > Almost certainly from your network stack; and my $$$ would
> be on your
> > > ISP/customer router.
> > >
> > So it's this way?
> > -the router (Linksys WRT350N) is creating the time out (or
> something
> > else in the "subsystem")
> > -it aborts the mission and somehow signals Evolution, which
> then pops up
> > the timed out message
> 
> 
> Sort of.  Your computer will send out ethernet packets to the
> internet
> via the router.  The packets that it sends out originate in
> Evolution
> via system calls.  Evolution doesn't create the packets,
> somewhere
> further down the ethernet software stack does that, evolution
> just tells
> the operating system what to put in the packets.
> 
> Once a packet is sent out, the system sits and waits for a
> response (as
> instructed by Evolution), if there is no response received in
> a specific
> time, then the operation times out.  The reasons that no
> packet has been
> received back are numerous - the remote end may be down, there
> may be a
> network problem, or some hardware may be malfunctioning.
>  There is no
> way to say for sure without extensive logging and tracing at
> both ends.
> 
> Once the network operation has timed out, the OS tells the
> originating
> program, i.e. Evolution, what has happened, and it is up to
> the program
> what it does then; Evolution happens to pop up a message about
> it,
> others may silently try again a number of times.  The timeout
> on the
> network operation is, I think, set by the OS, not the
> application.
> 
> The bottom line is that the timeout is NOT Evolution failing,
> it is
> merely reporting a failure elsewhere in the system.
> 
> P.
> 
> 
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list
> 
> 
> 
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[samarjit Adhikari]

Hi All,

I was facing similar issues of evolution timeout. My Evolution version was
3.10.2 from git source. Even I have observe that evolution was throwing
timeout very intermittently. Thus I have decided to investigate it further.
I could find that eds has implemented a "camel-network-service" which is
responsible for connecting any network socket and identifying network
change, calls "g_network_monitor_can_reach_async" with callback of
"network_service_can_reach_cb". The call
"g_network_monitor_can_reach_async" supposed to connect mail server and
transfer the handle to Evolution to use. It was a gio call and my gio
version is 2.38.1. Evolution was very dependent on this call and will
misbehave if such call "g_network_monitor_can_reach_async" misbehaves. I
have observed that the above mentioned call some time returns without
actually connecting to the mail server(verified through wireshark) and in
that case Evolution failed to connect showing "Timeout". Further looking
into the code of gio implementation I could find that gio keep caching all
network connections e.g. first time if evolution able to connect the mail
server, gio will cache it and if you reopen evolution the call
"g_network_monitor_can_reach_async" will return some time without
connecting the mail server explicitly and such behavior continues till
cache become invalid.

It is very annoying and could be a bug of GIO module rather than Evolution
stack.
I did not investigate further in GIO side due to time crunch , but I
believe it would certainly help in isolating evolution behavior from GIO.

With regards,
Samarjit

With regards,
Samarjit


On Mon, Dec 2, 2013 at 12:12 AM, Pete Biggs  wrote:

>
> > >
> > > Almost certainly from your network stack; and my $$$ would be on your
> > > ISP/customer router.
> > >
> > So it's this way?
> > -the router (Linksys WRT350N) is creating the time out (or something
> > else in the "subsystem")
> > -it aborts the mission and somehow signals Evolution, which then pops up
> > the timed out message
>
> Sort of.  Your computer will send out ethernet packets to the internet
> via the router.  The packets that it sends out originate in Evolution
> via system calls.  Evolution doesn't create the packets, somewhere
> further down the ethernet software stack does that, evolution just tells
> the operating system what to put in the packets.
>
> Once a packet is sent out, the system sits and waits for a response (as
> instructed by Evolution), if there is no response received in a specific
> time, then the operation times out.  The reasons that no packet has been
> received back are numerous - the remote end may be down, there may be a
> network problem, or some hardware may be malfunctioning.  There is no
> way to say for sure without extensive logging and tracing at both ends.
>
> Once the network operation has timed out, the OS tells the originating
> program, i.e. Evolution, what has happened, and it is up to the program
> what it does then; Evolution happens to pop up a message about it,
> others may silently try again a number of times.  The timeout on the
> network operation is, I think, set by the OS, not the application.
>
> The bottom line is that the timeout is NOT Evolution failing, it is
> merely reporting a failure elsewhere in the system.
>
> P.
>
>
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list
>
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Pete Biggs]

> > 
> > Almost certainly from your network stack; and my $$$ would be on your
> > ISP/customer router.
> > 
> So it's this way?
> -the router (Linksys WRT350N) is creating the time out (or something
> else in the "subsystem")
> -it aborts the mission and somehow signals Evolution, which then pops up
> the timed out message

Sort of.  Your computer will send out ethernet packets to the internet
via the router.  The packets that it sends out originate in Evolution
via system calls.  Evolution doesn't create the packets, somewhere
further down the ethernet software stack does that, evolution just tells
the operating system what to put in the packets.

Once a packet is sent out, the system sits and waits for a response (as
instructed by Evolution), if there is no response received in a specific
time, then the operation times out.  The reasons that no packet has been
received back are numerous - the remote end may be down, there may be a
network problem, or some hardware may be malfunctioning.  There is no
way to say for sure without extensive logging and tracing at both ends.

Once the network operation has timed out, the OS tells the originating
program, i.e. Evolution, what has happened, and it is up to the program
what it does then; Evolution happens to pop up a message about it,
others may silently try again a number of times.  The timeout on the
network operation is, I think, set by the OS, not the application.

The bottom line is that the timeout is NOT Evolution failing, it is
merely reporting a failure elsewhere in the system.

P.


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Eric Beversluis]

On Sat, 2013-11-30 at 17:13 -0500, Adam Tauno Williams wrote:
> On Sat, 2013-11-30 at 11:49 -0500, Eric Beversluis wrote:
> > 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? 
> 
> Depends on what you mean by "creates a time out".  The technical answer
> in yes - any application that performs I/O [the includes network I/O]
> can [and should] raise a time-out exception if an operation times out.
> 
> Evolution almost certainly does not *cause* a time-out;  the time-out is
> 'bubbling up' from the underlying subsystem(s).  Evolution does a *LOT*
> of I/O  - it is a powerful application and demanding of the underlying
> subsystems - so it may very well get an exception where something else
> may not.
> 
> Not a bug in Evolution.
> 
> > Where is the error message that the I/O
> > operation timed out coming from?
> 
> Almost certainly from your network stack; and my $$$ would be on your
> ISP/customer router.
> 
So it's this way?
-the router (Linksys WRT350N) is creating the time out (or something
else in the "subsystem")
-it aborts the mission and somehow signals Evolution, which then pops up
the timed out message

Whatever. I'm giving up on that particular wireless router and see if I
can avoid the problem that way.

Thanks


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Eric Beversluis]

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?

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Adam Tauno Williams]

On Sat, 2013-11-30 at 11:49 -0500, Eric Beversluis wrote:
> 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? 

Depends on what you mean by "creates a time out".  The technical answer
in yes - any application that performs I/O [the includes network I/O]
can [and should] raise a time-out exception if an operation times out.

Evolution almost certainly does not *cause* a time-out;  the time-out is
'bubbling up' from the underlying subsystem(s).  Evolution does a *LOT*
of I/O  - it is a powerful application and demanding of the underlying
subsystems - so it may very well get an exception where something else
may not.

Not a bug in Evolution.

> Where is the error message that the I/O
> operation timed out coming from?

Almost certainly from your network stack; and my $$$ would be on your
ISP/customer router.


-- 
Adam Tauno Williams  GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Patrick O'Callaghan]

On 6 November 2013 00:48, Bart  wrote:

> No.  It seems to stay the same.  I've tried a different modem just to
> eliminate that possibility.  Your explanation seems reasonable.  I do
> have another problem with the cable that they (the cable company) do not
> seem to be able to figure out.  I simply use the DSL connection most of
> the time.
>

This kind of weirdness can sometimes be caused by a mismatch in MTUs on the
two networks, but I'm not expert enough to give you specific advice.
However you could try reducing your machine's MTU to 576 (the lowest
standard value) to see if it makes a difference. See Google for how to do
this on Linux.

poc
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Bart]

On Tue, 2013-11-05 at 10:44 -0500, Adam Tauno Williams wrote:
> On Mon, 2013-10-28 at 15:26 -0600, Bart wrote:
> > 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,
> > While connected to the DSL connection, everything works well.  However,
> > when connected to the cable, I get a notice that the connection has
> > timed out on random accounts.  That is, if I do a Send/Receive, one or
> > more accounts will time out.  Not  the same ones, different accounts
> > each time.  This leads me to think it is not in evolution, but in the
> > internet connection provided by the cable company.
> 
> This sounds to me like a bad or overloaded Enterprise-NAT is in the mix.
> If you reboot your cable-modem/router does it work immediately following
> that?  And then after awhile works less well?
> 

No.  It seems to stay the same.  I've tried a different modem just to
eliminate that possibility.  Your explanation seems reasonable.  I do
have another problem with the cable that they (the cable company) do not
seem to be able to figure out.  I simply use the DSL connection most of
the time.

Bart

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Adam Tauno Williams]

On Mon, 2013-10-28 at 15:26 -0600, Bart wrote:
> 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,
> While connected to the DSL connection, everything works well.  However,
> when connected to the cable, I get a notice that the connection has
> timed out on random accounts.  That is, if I do a Send/Receive, one or
> more accounts will time out.  Not  the same ones, different accounts
> each time.  This leads me to think it is not in evolution, but in the
> internet connection provided by the cable company.

This sounds to me like a bad or overloaded Enterprise-NAT is in the mix.
If you reboot your cable-modem/router does it work immediately following
that?  And then after awhile works less well?

-- 
Adam Tauno Williams  GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Bart]

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.
> 

I have one thing to add about this situation.  I'm using evo 3.8.5 and
have 12 pop accounts.  I have both a cable connection and a DSL
connection at my location.  I can simply change the cable between the
router and the modem, make one change in the router settings, and I am
connected to either the cable or DSL.

While connected to the DSL connection, everything works well.  However,
when connected to the cable, I get a notice that the connection has
timed out on random accounts.  That is, if I do a Send/Receive, one or
more accounts will time out.  Not  the same ones, different accounts
each time.  This leads me to think it is not in evolution, but in the
internet connection provided by the cable company.

One other thing that may or may not be related.  I cannot configure my
router remotely when it is connected to the cable, but can when
connected to the DSL.  This occurs on different routers so it is not in
my system.  My cable ISP insists they do not block any ports and,
obviously, my firewall is not involved as everything works while
connected to DSL.

This internet stuff is so much fun!

Bart

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Adam Tauno Williams]

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.

-- 
Adam Tauno Williams  GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Eric Beversluis]

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.

Thanks.

On Thu, 2013-10-10 at 21:56 -0400, Carpetnailz wrote:
> I'm running Evo 3.4.4 on Fedora 17. 
> 
> About half the time or so when I do Send/Receive, I get this error
> message:
> 
> Error while Fetching Mail.
> Could not connect to mail.researchintegration.org: I/O operation timed
> out.
> 
> Sometimes one or two of the three accounts I'm connected to there
> download before the error occurs, sometimes none. About half the time it
> works OK.
> 
> The host of my domain says they've checked and their system is ok. Also,
> my wife, using Mac Mail, doesn't have these problems. And the problems
> occur for me at work as well as at home. My other internet connections
> do not seem problematic.
> 
> I tried switching from tls to no encryption, but that did not help.
> 
> Thanks.
> 
> 
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Ralf Mardorf]

On Mon, 2013-10-14 at 17:49 -0400, Carpetnailz wrote:
> It's frustrating that the linux community can't hold to "if it ain't
> broke, don't fix it."

Assumed you can live with outdated software, that only will get security
updates, Debian stable might be what you want, but I didn't maintain a
Debian install since years. If you want to be in sync with upstream, but
anyway a stable distro, then Arch Linux might fit to your needs. Suse
and *buntu indeed are a risk in my experiences. I don't have valid
experiences with Fedora and my Suse is outdated, so things might have
changed. I still maintain an *buntu install, but my main Linux is Arch.
There might be other stable distros too.

Arch isn't perfect, but for my needs the best of all distros I "know".


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Pascal Hasko Bernhard]

Hi all,

On Mon, 2013-10-14 at 17:49 -0400, Carpetnailz wrote:
> Well I tried that and managed to brick my computer. That's why I was
> still using Fed 17! Every time I upgrade something goes wrong and it's a
> two-day catastrophe, as the installers don't like something or other
> about the hardware. This time I never was able to get my box to boot,
> even tho the installation seemed to go right any number of times.
> Something screwy with UEFI which neither Fed 19 nor openSUSE could
> manage on my computer. Had to move eventually to a different box and
> update the existing Ubuntu 12.04 LTS on it.It's frustrating that the
> linux community can't hold to "if it ain't broke, don't fix it."
> 
> Anyway now on a new box with an updated version of Ubuntu 12.04 LTS and
> running evo 3.4.2 I'm still getting the same problem. Omnis, my host,
> tells me they've checked and there's nothing wrong at their end.
> 
> Also, my wife never has this problem with her Mac mail.So the only
> constant here seems to be Evolution.
> 
> Since the problem is very intermittent--the connection will fail and
> then work right the next minute--I wonder if it's a time-out triggered
> by some setting in Evo? The error message is: "Could not connect to
> mail.research.org. TCP connection was reset by peer." 

I can confirm the issues Carpetnailz is having:


On a quite regular basis, every other day or so, I get similiar error
messages on several different mail accounts (two Gmail, a Yahoo, and a
Live mail account as well as my local LUG mail account). This does not
happen with all accounts simultaneously, they seem to take turns. But
that is only my subjective impression, I'll have to track the order
which mail account the messages refer to each time.

Here on my Sabayon 13.08 I have Evolution 3.8.5 which should still be
supported. I run Evolution mail on a desktop machine with MATE desktop
1.6 and on a laptop with GNOME 3.8.

Same Evolution behavior on a Debian Testing machine. I'm not quite sure
about the exact Evolution version should be 3.8.2, I will check next
time when I boot up that computer again, currently it is not running.

Pascal


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Carpetnailz]

Well I tried that and managed to brick my computer. That's why I was
still using Fed 17! Every time I upgrade something goes wrong and it's a
two-day catastrophe, as the installers don't like something or other
about the hardware. This time I never was able to get my box to boot,
even tho the installation seemed to go right any number of times.
Something screwy with UEFI which neither Fed 19 nor openSUSE could
manage on my computer. Had to move eventually to a different box and
update the existing Ubuntu 12.04 LTS on it.It's frustrating that the
linux community can't hold to "if it ain't broke, don't fix it."

Anyway now on a new box with an updated version of Ubuntu 12.04 LTS and
running evo 3.4.2 I'm still getting the same problem. Omnis, my host,
tells me they've checked and there's nothing wrong at their end.

Also, my wife never has this problem with her Mac mail.So the only
constant here seems to be Evolution.

Since the problem is very intermittent--the connection will fail and
then work right the next minute--I wonder if it's a time-out triggered
by some setting in Evo? The error message is: "Could not connect to
mail.research.org. TCP connection was reset by peer." 

On Fri, 2013-10-11 at 11:28 +0200, Andre Klapper wrote:
> On Thu, 2013-10-10 at 21:56 -0400, Carpetnailz wrote:
> > I'm running Evo 3.4.4 on Fedora 17. 
> 
> Fedora 17 saw its end of life in July 2013.  Please update to supported
> software that still receives security fixes.
> 
> andre


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Andre Klapper]

On Thu, 2013-10-10 at 21:56 -0400, Carpetnailz wrote:
> I'm running Evo 3.4.4 on Fedora 17. 

Fedora 17 saw its end of life in July 2013.  Please update to supported
software that still receives security fixes.

andre
-- 
Andre Klapper  |  ak...@gmx.net
http://blogs.gnome.org/aklapper/

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Re: [Evolution] I/O operation timing out

[Patrick O'Callaghan]

On 11 October 2013 02:56, Carpetnailz
wrote:

> I'm running Evo 3.4.4 on Fedora 17.
>

F17 is a no longer supported version of Fedora. Updating to F19 will also
get you a more recent version of Evo which may solve the problem.

poc
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Evolution] I/O operation timing out

[Carpetnailz]

I'm running Evo 3.4.4 on Fedora 17. 

About half the time or so when I do Send/Receive, I get this error
message:

Error while Fetching Mail.
Could not connect to mail.researchintegration.org: I/O operation timed
out.

Sometimes one or two of the three accounts I'm connected to there
download before the error occurs, sometimes none. About half the time it
works OK.

The host of my domain says they've checked and their system is ok. Also,
my wife, using Mac Mail, doesn't have these problems. And the problems
occur for me at work as well as at home. My other internet connections
do not seem problematic.

I tried switching from tls to no encryption, but that did not help.

Thanks.


___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list