[Evolution] Calendar-EWS generates zombies [evolution]
Hi, I have been using Evolution with EWS on an exchange server 2010 for a while. The calendar part has always been a bit instable, but not systematically so. Recently, maybe with the update to 3.10.3, the Calendar stopped working. When I switch to the Calendar for the first time, I get two zombies [evolution] The my calendar shows on the left but the main window does not show any entries. I can still use all other functionality from the exchange server, Mail, Contacts, Tasks, Memos. I have been looking through the archive, but I could not find any posts for 3.10.3 generating [evolution] . I looked into the documentation to activate debugging, but I am not sure which option (and how) to activate. Anybody with similar problems or ideas how to solve this? I would really appreciate this, as Evolution seems to be the only way to use Exchange functionalities on Ubuntu (13.10). /Michael 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] Calendar-EWS generates zombies [evolution]
On Tue, 2014-02-18 at 10:16 +, evolution-list-requ...@gnome.org wrote: > >From a terminal do > > EWS_DEBUG=2 evolution > > I don't know why the EWS debugging things were omitted from > > https://wiki.gnome.org/Apps/Evolution/Debugging > Thank you. I piped the information into a file ( &> ). I am however not sure what to look after. The zombies are still created. Evolution does no longer crash, but the calendar is only incompletely synchronized. Only events that I have entered today (from a different client) show up. Manual refresh has no effect. > > EWS does work on Evo 3.10.3, it may be that there is something odd > with > the specific configuration you are using (either at your end or the > Exchange end). It may just be that you need to clean the cache/index > files - but I don't know enough about EWS and calendars to know if > that > could be an issue. It would be great to get a hint on how to clean the cache. I cannot influence the Exchange end. > > If all else fails, then have a look at Davmail - it's a separate > program > that runs on your own machine that provides standard port interfaces > to > an Exchange server - i.e. you will see a CalDAV port locally that > connects to the Exchange calendar. It's not perfect, but it works. > >http://davmail.sourceforge.net/ > I will try if problems remain. > But it would be far better to work out why Evolution isn't doing the > correct thing. > I agree. /Michael 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] Calendar-EWS generates zombies [evolution]
> > > >From a terminal do > > > > > > EWS_DEBUG=2 evolution > > > > > > I don't know why the EWS debugging things were omitted from > > > > > > https://wiki.gnome.org/Apps/Evolution/Debugging > > > > > > > Thank you. I piped the information into a file ( &> ). I am however > not > > sure what to look after. > > Basically any errors, permission denied, timeouts that sort of thing. > OK, here is all preg on error / denied /timeout: Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 14: out of memory Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 23: out of memory Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 32: out of memory *** NSPlugin Wrapper *** ERROR: failed to execute NSPlugin viewer > http://schemas.xmlsoap.org/soap/envelope/"; xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://schemas.microsoft.com/exchange/services/2006/types"; Version="Exchange2007_SP1"/>http://schemas.microsoft.com/exchange/services/2006/message s">http://schemas.microsoft.com/exchange/services/2006/types";>AllProperties...*** <http://schemas.microsoft.com/exchange/services/2006/types";>AllPropertiesH4sIAAAEAO29B2AcSZYlJi9tynt/SvVK1+B0oQiAYBMk2JBAEOzBiM3mkuwd aUcjKasqgcplVmVdZhZAzO2dvPfee++999577733ujudTif33/8/XGZkAWz2zkrayZ4hgKrIHz9 +fB8/In6NX+PX/TXoOfjF+w+P9+/d3znePnlwfLC9f3xyb/vJyZOT7Wd7Tw5Onjx49vD+/Z1f8t 3X49fXy+nrNmvzk2yZ1de/xqP3f/NZVc7y+mz2azx8/3d/Mq+bolr+GjsnZZEvW/7s9z95sPN09 9Od/e2dh6cPtvcPHp5vP9k9eLL99Mm9ew+ePDy+92zn2a/x6cm6fp3Xl3n9RbYszvOmvd17TJ/k 1/g1fhtCQzD/dpHXWT2dXwOrX+M3p6936P9jtPttfuZ7/2P1h/0tL/6kf+XX/x3/2r/wV/7Bv+a v8Tv+Hv/zn//t/+VPO/5zf6/mD7nzD/7qP+PX+Lv/5uf/y3/xa/wav+av8ZvQ/+n5Dej/vzt+eU 8oJ3/y//1r/Bq/znu+9bf+Tf/oX4e+N731t/71v+tP/02/0953/oG/d/yrf9nLf/ffRKtf8bvd9 Fasr3/sD3v/t/6WxR/xV7//WzSuv+drvfX3vv9bRPn/4/3for7+2q/11l/1td76GjQkvvzvvtZb /+3X4Kjf6e/7F96/L+KoP/T936L5+j9/jV/j13vvt/6UX/Nr9fW//xq/xq/1/m/96l/j1/i13/+ t/4vV9/u99fx/+W++xrie/y//9fu/9bd978fevP9bxL1/99d66+/7Wm/9Ne//1t/2vd/g/3z/t6 ivv/793/rbyt/4T3l/+fot/uz//T/6Gm/9Rb/sa1iH3+Iv+p//5K/x1l/6Z//rX+utf+RrvfV3f Y23/vLmH/0ab/1Vv93fiLe+jklXx+C3ofYRlflb/bG/0R/w2/0FLz8AaIQn/+bf+uG3/uzp9z4A aNRd+PiP+Ofn7+ub3IDp3/o/f+u3+Df/k7/7GwX6t1T/6P/2a/3Nz3/HbxTo3/o3v/of/5R/7W/ 8G98TqHFhhoC++WU/8b8+v/+eQDdj+jc//xW/1R/6X/0uv+E3CvRv/Zt/i//r//pffoN/7BsG+m uk9z5ef/cbBvob7LY//m/9b98oUKLpr/fox/6YP/MDgEaUyp/2X/zH/+Qv+ur3/0aBkg/2L72c/ c7/8QcAjYnp/5g8Ox7/im8UKNH0t/sdkl/vm6Xpr/Fr/LLf+B/79/6q//EbBfpb/FWPX18l/8Df 8QFAo8P/zf7Cv+fln/8BQCPD/zX/kj/sb/irJr/pBwCNYvrr/C8/8fs+/wCgMZrOfvOr***> NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client connection *** NSPlugin Wrapper *** ERROR: failed to execute NSPlugin viewer *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client connection < HTTP/1.1 401 Unauthorized < Soup-Debug-Timestamp: 1392805687 < Soup-Debug: ESoapMessage 1 (0x7fc097021dd0) < Set-Cookie: mail.liu.se=R408630383; path=/ < Server: Microsoft-IIS/7.5 < Set-Cookie: exchangecookie=...; expires=Thu, 19-Feb-2015 10:28:07 GMT; path=/; HttpOnly < WWW-Authenticate: ... < WWW-Authenticate: Negotiate < X-Powered-By: ASP.NET < Date: Wed, 19 Feb 2014 10:28:06 GMT < Content-Length: 0 > > The zombies are still created. Evolution does > > no longer crash, but the calendar is only incompletely synchronized. > > Only events that I have entered today (from a different client) show > up. > > Manual refresh has no effect. > > Try creating a new Linux account, then from that account create the > EWS > account in Evolution. This will start you with a new clean > configuration and see if that then works correctly. If it does, then > you will know it's something to do with the configuration and not the > server or the install of Evolution. I will try that as a third step, because it will take a while to get all my 25 k mails on sync .. Also the setup of EWS was laborious since auto-discover did not work. I would prefer to test the step below first. > > > > > > > > > EWS does work on Evo 3.10.3, it may be that there is something odd > > > with > > > the specific configuration you are using (either at your end or > the > > > Exchange end). It may just be that you need to clean the > cache/index > > > files - but I don't know enough about EWS and calendars to know if > > > that > > > could be an issue. > > > > It would be great to get a hint on how to clean the cache. I cannot > > influence the Exchange end. > > The cache is stored in ~/.cache/evolution/calendar
Re: [Evolution] Calendar-EWS generates zombies [evolution]
>>Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 14: out of >>memory >>Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 23: out of >>memory >>Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 32: out of >>memory > >Are you really running out of memory? If so, then that will cause you >lots of problems. That may be why you are getting zombies. Hardly. It is a machine with 8 GB. I think I have seen the message for other software two and it was never a problem in practice. I think EVO always showed this, but it worked fine earlier. > > >>< HTTP/1.1 401 Unauthorized >>< Soup-Debug-Timestamp: 1392805687 >>< Soup-Debug: ESoapMessage 1 (0x7fc097021dd0) >>< Set-Cookie: mail.liu.se=R408630383; path=/ >>< Server: Microsoft-IIS/7.5 >>< Set-Cookie: exchangecookie=...; expires=Thu, 19-Feb-2015 10:28:07 GMT; >>path=/; HttpOnly >>< WWW-Authenticate: ... >>< WWW-Authenticate: Negotiate >>< X-Powered-By: ASP.NET >>< Date: Wed, 19 Feb 2014 10:28:06 GMT >>< Content-Length: 0 > >I don't think the 401 is a good sign ... It is the only 401. But I have no idea what the problem is here. > > >>> >>> The cache is stored in ~/.cache/evolution/calendars - you could try >>> shutting down Evolution (and all the backend processes), and rename >>> that >>> folder - Evolution should recreate it all when you restart. >>How do I shut-down the backend processes? I google it, but could only >>find >>people wanting to remove EVO altogether. 'service' does not show >>evolution >>backends. > >Service only shows system things, not user land things. > >After you shutdown Evolution (do 'evolution --force-shutdown' if >necessary) you need to do > > ps -ef | grep evolution > >to see any background Evolution processes that are still running (the >gnome calendar gets info from Evo and the alarm notify daemon is left >running). Kill the processes using the 'kill' command. I tried, but the processes are relaunched all the time. I tried to move the cache, but the destination was removed automatically and now EVO crashes completely as soon as I switch to the calendar view. I will try once more as instructed below. If also that fails, I will try on a different account. Thanks Michael > >If you really want to be sure, reboot your system, but don't login. >Switch to a console (Ctl-Alt-F2) and login there. Make sure nothing Evo >related is running and then rename the cache folder. Logout of the >console, switch back to the GUI (Alt-F1) and go from there. > >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] Calendar-EWS generates zombies [evolution]
>>>Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 14: out of >>>memory >>>Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 23: out of >>>memory >>>Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 32: out of >>>memory >> >>Are you really running out of memory? If so, then that will cause you >>lots of problems. That may be why you are getting zombies. > >Hardly. It is a machine with 8 GB. I think I have seen the message for >other software two and it was never a problem in practice. I think EVO >always showed this, but it worked fine earlier. > >> >> >>>< HTTP/1.1 401 Unauthorized >>>< Soup-Debug-Timestamp: 1392805687 >>>< Soup-Debug: ESoapMessage 1 (0x7fc097021dd0) >>>< Set-Cookie: mail.liu.se=R408630383; path=/ >>>< Server: Microsoft-IIS/7.5 >>>< Set-Cookie: exchangecookie=...; expires=Thu, 19-Feb-2015 10:28:07 GMT; >>>path=/; HttpOnly >>>< WWW-Authenticate: ... >>>< WWW-Authenticate: Negotiate >>>< X-Powered-By: ASP.NET >>>< Date: Wed, 19 Feb 2014 10:28:06 GMT >>>< Content-Length: 0 >> >>I don't think the 401 is a good sign ... > >It is the only 401. But I have no idea what the problem is here. > >> >> The cache is stored in ~/.cache/evolution/calendars - you could try shutting down Evolution (and all the backend processes), and rename that folder - Evolution should recreate it all when you restart. >>>How do I shut-down the backend processes? I google it, but could only >>>find >>>people wanting to remove EVO altogether. 'service' does not show >>>evolution >>>backends. >> >>Service only shows system things, not user land things. >> >>After you shutdown Evolution (do 'evolution --force-shutdown' if >>necessary) you need to do >> >> ps -ef | grep evolution >> >>to see any background Evolution processes that are still running (the >>gnome calendar gets info from Evo and the alarm notify daemon is left >>running). Kill the processes using the 'kill' command. > >I tried, but the processes are relaunched all the time. I tried to move >the cache, but the destination was removed automatically and now EVO >crashes completely as soon as I switch to the calendar view. I will try >once more as instructed below. If also that fails, I will try on a >different account. Experience with the new, empty account: EVO freezes when switching to Calendar. I let it go and after some time items from my account pop up. I could change back to Email. However, when I switched back to Calendar and pressed on work-week view, it freezes again. I checked the process table, EVO is on about 43 minutes, while running for about 3 hours. My machine has a Xeon E5-1620 (8x3.7GHz). EVO calendar backend is at 7 minutes. While writing: EVO is still frozen, more than 10 minutes now. Any ideas? As said before, some versions earlier, EVO was working quite OK with the Exchange server. Just about one crash per day (~100 emails per day). Michael > >Thanks > >Michael > >> >>If you really want to be sure, reboot your system, but don't login. >>Switch to a console (Ctl-Alt-F2) and login there. Make sure nothing Evo >>related is running and then rename the cache folder. Logout of the >>console, switch back to the GUI (Alt-F1) and go from there. >> >>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] Calendar-EWS generates zombies [evolution]
>Experience with the new, empty account: >EVO freezes when switching to Calendar. I let it go and after some time >items from my account pop up. >I could change back to Email. However, when I switched back to Calendar >and pressed on work-week view, it freezes again. > >I checked the process table, EVO is on about 43 minutes, while running for >about 3 hours. My machine has a Xeon E5-1620 (8x3.7GHz). EVO calendar >backend is at 7 minutes. > >While writing: EVO is still frozen, more than 10 minutes now. Follow-up: after 15 minutes it came back. Retried with my original account and let it go over night. EVO was up to 1 hour process time and Calendar-backend was up to 45 minutes. Everything was synced then. I deleted one character in one event and the whole thing freezes again. So my understanding is that EVO has a serious performance issue since some update in the past weeks, which exactly is difficult to say. Michael > >Any ideas? > >As said before, some versions earlier, EVO was working quite OK with the >Exchange server. Just about one crash per day (~100 emails per day). > ___ 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] Calendar-EWS generates zombies [evolution]
Hi, I did not really have time to follow-up the latest suggestions and now I gave up. After updating to Ubuntu 14.04, my system is stone-dead. I have no time for searching the reason, so I will use Windows8 in the future. /Michael On 2/28/14 11:35 AM, "evolution-list-requ...@gnome.org" wrote: >Hello, > >I have seen similar behavior on EVO 3.10.4 as well. The Calendar suddenly >freezes. Specially when new meeting invitation comes it is hung with >"looking for invitation". and all the appointments in calendar vanishes. >Also the gnome calendar (drop down from date time on top panel) vanishes. > >The workaround for me is to kill the evolution-calendar-factory and >Evolution gets back the control and the calendar comes up also (most of >the >time this work around works). > >I am using Fedora 20 and Evolution is used with my calendar as well as >many >other shared calendar ( > 15). I have increased the connection time out in >Preferences to 20 seconds to see if the time out is causing any issue >in >the hung connections after a while (default is 120 seconds). > >Thanks for any input. BR, /Deepak ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
