I agree also, although I do have a new error in my osx syslog (I added some CR's to improve how it looks. In the actual log, this is all on 1 line):
Code:
Feb 2 09:34:07 mankind [0x0-0x389389].com.apple.iCal[38579]: 2008-02-02 09:34:07.268 iCalExternalSync[38867:10b] [ICalExternalSync ]NSException name:NSInvalidArgumentException reason:*** -[NSCFDictionary setObject:forKey:]: attempt to insert nil value (key: url)
Feb 2 09:34:16 mankind iCal[38579]: CalDAV CalDAVWriteEntityQueueableOperation failed: status 'HTTP/1.1 405 HTTP method PUT is not supported by this URL' request:\n\nBEGIN:VCALENDAR^M\nVERSION:2.0^M
\nPRODID:-//Apple Inc.//iCal 3.0//EN^M\nCALSCALE:GREGORIAN^M
\nBEGIN:VTIMEZONE^M
\nTZID:America/Phoenix^M
\nBEGIN:DAYLIGHT^M
\nTZOFFSETFROM:-0700^M
\nTZOFFSETTO:-0600^M
\nDTSTART:19670430T020000^M
\nRDATE:19670430T020000^M
\nTZNAME:MDT^M
\nEND:DAYLIGHT^M
\nBEGIN:STANDARD^M
\nTZOFFSETFROM:-0700^M
\nTZOFFSETTO:-0700^M
\nDTSTART:20001231T170000^M
\nRDATE:20001231T170000^M
\nTZNAME:MST^M
\nEND:STANDARD^M
\nEND:VTIMEZONE^M
\nBEGIN:VEVENT^M
\nSEQUENCE:1^M
\nTRANSP:OPAQUE^M
\nUID:5BCE5DC2-5D72-4181-B168-1224784AD1FD^M
\nDTSTART;TZID=America/Phoenix:20080202T100000^M
\nDTSTAMP:20080202T163415Z^M
\nSUMMARY:New Event^M
\nCREATED:20080202T163415Z^M
\nDTEND;TZID=America/Phoenix:20080202T110000^M
\nEND:VEVENT^M
\nEND:VCALENDAR^M
\n\n\n... response:\nHTTP/1.1 405 HTTP method PUT is not supported by this URL^M
\nDate: Sat, 02 Feb 2008 16:34:24 GMT^M
\nPragma: no-cache^M
\nContent-Type: text/html; charset=iso-8859-1^M
\nContent-Length: 1419^M
\nConnection: close^M
\n^M
\n<html>\n<head>\n<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>\n<title>Error 405 </title>\n</head>\n<body><h2>HTTP ERROR: 405</h2><pre>HTTP method PUT is not supported by this URL</pre>\n<p>RequestURI=/zimbra/</p><p><i><small><a href="http://jetty.mortbay.org/">Powered by Jetty://</a></small></i></p><br/>
\n<br/> \n<br/>
\n<br/> \n<br/> \n<br/>
\n<br/> \n<br/>
\n<br/> \n<br/> \n<br/>
\n<br/> \n<br/>
\n<br/> \n<br/> \n<br/>
\n<br/> \n<br/>
\n<br/> \n<br/> \n\n</body>\n</html>
I'm not sure if it matters, but I run all zimbra stuff via https, no port 80 here. However, during the upgrade, I did get a complaint of a port conflict with port 80. After the upgrade, I did run:
and then restarted zimbra.
This almost makes it seem like the calendar is being published via http and not https?
David