Hi, Hard to say what's up without seeing more information (such as any interesting error.log content), however there's a reasonably small update to 5.4-dev that has some key fixes made since 5.3.
http://trac.calendarserver.org/log/CalendarServer/branches/release/CalendarServer-5.4-dev <http://trac.calendarserver.org/log/CalendarServer/branches/release/CalendarServer-5.4-dev> There is one known issue in 5.3 regarding how we handle updating calendar event data when the format changes (as it has recently). In 5.3, the approach is to leave the data in the old format until it is requested, and then update it on the fly as it is vended to the client. This fails when there are enough events being 'touched' by the request that the processing time for doing the format upgrades exceeds the client's request timeout threshold. This is fixed in 5.4-dev. Be sure to have backups before you do anything :) -dre > On Feb 3, 2015, at 2:23 PM, Jacques Distler <dist...@golem.ph.utexas.edu> > wrote: > > * CalendarServer 5.3 > * Clients: Calendar.app on MacOSX and iOS. > > All of a sudden, I am getting a lot of > > [twext.web2.channel.http#error] Connection aborted - took too long to close > > errors in my logs -- essentially every time the client tried to manually > refresh the calendars. To be more precise, only certain clients (or > delegates) seem to be affected -- those with rather large calendars. > > I wonder if some internal limit on the server side has been exceeded, causing > the transaction to fail. > > Any pointers for debugging this would be appreciated. > > > _______________________________________________ > calendarserver-users mailing list > calendarserver-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/calendarserver-users
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-users
