On Feb 12, 2009, at 12:14, Sean McAvoy wrote:
On Feb 12, 2009, at 00:14, Sean McAvoy wrote:
On Feb 11, 2009, at 22:07, Cyrus Daboo wrote:
Hi Sean,
--On February 11, 2009 6:22:37 PM +0100 Sean McAvoy <smca...@ripe.net
> wrote:
What does the server's access.log and error.log look like for this
problem? Also, what are the timestamps on iCal's log entries? In
particular, it could be that iCal is timing out waiting on the
server (i.e. a performance issue rather than a limit).
I would hope it not a performance issue, its single quad core
with 4gb of
RAM :) acting as a OD Server and running the calendar server.
I've included a lot of the error log as nothing stands out for me,
perhaps for you?
access.log:
193.0.20.121 - smcavoy [11/Feb/2009:18:05:39 +0200] "PROPFIND
/calendars/__uids__/819B6FB2-066B-446C-854F-DC14DDD937D8/calendar/
HTTP/1.1" 207 496208 "-" "D AVKit/3.0.6 (653); CalendarStore/
3.0.6 (847);
iCal/3.0.6 (1273); Mac OS X/10.5.6 (9G55)" [80504.2 ms]
What do other PROPFINDs look like in terms of the [XXX ms] value
reported in the access.log? What does cpu and memory use show on
that machine?
Both memory and load are quite high, around 40-50% average usage
for CPU and 80% phys memory used.
Here is one of the problem calendars:
access.log
[12/Feb/2009:00:02:39 +0200] "PROPFIND /calendars/__uids__/
819B6FB2-066B-446C-854F-DC14DDD937D8/ HTTP/1.1" 207 5184 "-"
"DAVKit/3.0.6 (653); CalendarStore/3.0.6 (847); iCal/3.0.6 (1273);
Mac OS X/10.5.6 (9G55)" [4048.2 ms]
error.log
2009-02-12 00:02:38+0100 [-] [caldav-8009] [AMP,client] PROPFIND /
calendars/__uids__/819B6FB2-066B-446C-854F-DC14DDD937D8/ HTTP/1.1
2009-02-12 00:02:40+0100 [-] [caldav-8009] [AMP,client] PROPFIND /
calendars/__uids__/819B6FB2-066B-446C-854F-DC14DDD937D8/calendar/
HTTP/1.1
iCal client:
2/12/09 12:04 iCal[4703] CalCalDAVCalendarSource: Error
Domain=AYErrorDomain Code=2 UserInfo=0x167c7a20 "Async Operation
timed out"
2/12/09 12:04 iCal[4703] The server at /calendars/__uids__/
819B6FB2-066B-446C-854F-DC14DDD937D8/calendar/ responded with the
error:
"Async Operation timed out"
2/12/09 12:04 iCal[4703] The server at /calendars/__uids__/
819B6FB2-066B-446C-854F-DC14DDD937D8/calendar/ responded with the
error:
"Async Operation timed out"
many PROPFINDs are less then 100ms all problem ones are 3000ms+
I will look into possible network issues.
I connected a system to the same VLAN as the calendar server,
calendars with about 1500 events work some of the time but take
sometime. 3000+ event calendars still do not work at all.
I will move a few of the large calendars to a almost unused
similarly spec'd system to see if a single user downloading the
calendar works.
Has there been many tests of large calendars + iCal clients?
I have tried this and found the same basic problem, other users cannot
access calendars with lots of events (tested 900-9500 event calendars).
Do you have any other suggestions on how to narrow down the problem?
Thanks!
Thanks!
Note that according to the access log the server did send back a
response for that PROPFIND, so I find it a little odd that the
client saw nothing. Are there any intermediary devices (firewalls,
routers etc) between the client and server?
--
Cyrus Daboo
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
