After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 374782 - Lost connection to evolution exchange backend process
Lost connection to evolution exchange backend process
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.8.x
Other All
: Normal major
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2006-11-13 17:16 UTC by Robert Banfield
Modified: 2008-08-22 08:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
DebugLevel4 Logfile (14.29 KB, text/plain)
2006-11-13 17:19 UTC, Robert Banfield
Details
PNG screen capture of the evolution-exchange-storage process using all remaining CPU (202.33 KB, image/png)
2006-12-15 18:55 UTC, Andrig Miller
Details
This is the system call trace output showing what the evolution-exchange-storage process seems to be doing. (7.85 KB, text/plain)
2006-12-15 19:52 UTC, Andrig Miller
Details

Description Robert Banfield 2006-11-13 17:16:57 UTC
Please describe the problem:
I cannot read my email.  I can read the message headers.  

Steps to reproduce:
0.  Reboot computer
1.  killall evolution-data-server-1.8   [optional]
2.  killall evolution-exchange-storage  [optional]
3.  setenv E2K_DEBUG 4
4.  evolution >& evo.log

Actual results:
[Message Box]
Error while Refreshing folder.
Lost connection to Evolution Exchange backend process

It appears to have downloaded the message headers, but does not get any of the body.  If a message is clicked on, the body reads:

Unable to retrieve message
Lost connection to evolution exchange backend process

Expected results:
I should be able to read my email

Does this happen every time?
Yes

Other information:
I have found a way to workaround.

1.  Place evolution into offline mode (icon on bottom left)
2.  Restart evolution
3.  Place evolution into online mode (icon on bottom right)

Now I can read my mail.  If at this point, the program is restarted, it will once again lose its connection.  I am unsure what will happen if a new message is received at this time.  I only know that I can read my existing mail.

[System Information]
Fedora Core 6
Kernel 2.6.18-2849.fc6  X86_64 X86_64

[Evolution Information]
% yum list installed | grep evol
beagle-evolution.x86_64                  0.2.10-6.fc6           installed       
evolution.x86_64                         2.8.1.1-3.fc6          installed       
evolution.i386                           2.8.1.1-3.fc6          installed       
evolution-connector.x86_64               2.8.1-1.fc6            installed       
evolution-data-server.x86_64             1.8.1-1.fc6            installed       
evolution-data-server.i386               1.8.1-1.fc6            installed       
evolution-data-server-devel.x86_64       1.8.1-1.fc6            installed       
evolution-data-server-devel.i386         1.8.1-1.fc6            installed       
evolution-devel.i386                     2.8.1.1-3.fc6          installed       
evolution-devel.x86_64                   2.8.1.1-3.fc6          installed       
evolution-sharp.x86_64                   0.11.1-10.fc6          installed       
evolution-webcal.x86_64                  2.7.1-6                installed       
mail-notification-evolution-plugin.x86_6 3.0-10.fc6             installed       

I have an evo.log file that I will attach shortly.
Comment 1 Robert Banfield 2006-11-13 17:19:45 UTC
Created attachment 76499 [details]
DebugLevel4 Logfile

Logfile for the bug witnessed at debug level 4.
Comment 2 Robert Banfield 2006-12-05 14:39:02 UTC
Is this bug being worked on, cared about, etc?  Its been up here for 3 weeks and I haven't heard anything.  
Comment 3 Robert Banfield 2006-12-06 19:50:36 UTC
Still present in the recent download of 2.8.2.1
Comment 4 Andrig Miller 2006-12-15 18:55:29 UTC
Created attachment 78444 [details]
PNG screen capture of the evolution-exchange-storage process using all remaining CPU

This is the screen shot of the evolution-exchange-storage process using up all the remaining CPU cycles.
Comment 5 Andrig Miller 2006-12-15 19:52:21 UTC
Created attachment 78446 [details]
This is the system call trace output showing what the evolution-exchange-storage process seems to be doing.

This is the strace output showing the system calls that the evolution-exchange-storage process is doing.  These happen very fast, as this was only a few seconds of capture. I had to edit the file to shorten it, as it was 30.9MB in just a few seconds of capture.
Comment 6 Andrig Miller 2006-12-15 19:55:26 UTC
I am now, suddenly, have the same problems.  The two attachments are a screen shot that shows the evolution-exchange-storage process consuming all available CPU cycles when the error occurs, and this continues indefinitely.  The other attachement is an strace output of what that process is doing.  Polling quite a few sockets.

I am using Evolution 2.8.2.1 on Fedora Core 6, so it is happening for me on a newer version.

Also, the workaround above does not work for me, so I cannot access my inbox anymore at all through Evolution.
Comment 7 Robert Banfield 2007-01-23 23:27:40 UTC
Another workaround is to delete the ~/.evolution folder entirely.  I got fed up waiting for an update on this bug and just tried that instead.  Evolution has now been up and running fine for several days.  Hopefully this helps out others.
Comment 8 Peter 2007-04-01 15:54:07 UTC
This bug was also reported in our bugzilla: bugs.gentoo.org/157241

This is reproducible in Downgrading evolution-exchange-2.8.2. Also Vladimir suggested better solution than just to remove ~/.evolution:

"What did work was to rename ~/.evolution and to copy the addressbook, calendar
and signatures directories to a newly created ~/.evolution."

HTH.

Comment 9 Raphael Bosshard 2008-02-25 11:31:31 UTC
I can confirm this bug; it got worse in the lastest developement releases (2.21.91) and occurs now evertime I use evolution-exchange. After one or two operations I have to "--force-shutdown" Evolution. 


Are there any informations I might provide?

Btw; this also affects the clock-applet; if evolution-exchange is installed, a click on the clock-applet will bring down the whole gnome-panel. But I better file a separate bug for that...
Comment 10 Akhil Laddha 2008-07-14 06:27:59 UTC
bug 420503 should solve most of 'lost connection' crashes. Do you still see in current stable 2.22.3 ? can you please provide gdb traces when evolution or exchange process dies. Please see http://live.gnome.org/GettingTraces
for more information on how to do so. Thanks in advance!
Comment 11 Akhil Laddha 2008-08-22 08:12:29 UTC
Please feel free to reopen this bug if the problem still occurs with a newer
version of GNOME 2.22.3.1, thanks.