Hi thank you for your time... This is the same for creating, moving, delete Calendarsever 2.4 does not have the same problem only 3.2, 4.2 on this system
Here is the delete operation failing... 2013-03-07 11:41:32-0500 [-] [caldav-1] [HTTPChannel,23,::ffff:192.168.1.38] [twext.web2.server#info] DELETE /calendars/__uids__/admin/calendar/4BB3FD49-05EC-46FE-A958-66C790F462B9.ics HTTP/1.1 2013-03-07 11:41:32-0500 [-] [caldav-1] [HTTPChannel,24,::ffff:192.168.1.38] [twext.web2.server#info] GET /calendars/__uids__/admin/calendar/4BB3FD49-05EC-46FE-A958-66C790F462B9.ics HTTP/1.1 2013-03-07 11:41:32-0500 [-] [caldav-1] [HTTPChannel,24,::ffff:192.168.1.38] [twistedcaldav.directory.digest.DigestCredentialsMemcache#debug] Getting Cache Token for '23068977201759756079232744263502251584903490272716206165' 2013-03-07 11:41:32-0500 [-] [caldav-1] [HTTPChannel,24,::ffff:192.168.1.38] [twistedcaldav.memcachepool.MemCachePool#debug] Busied client: <twistedcaldav.memcachepool.PooledMemCacheProtocol instance at 0x34df5a8> 2013-03-07 11:41:32-0500 [-] [caldav-1] [HTTPChannel,24,::ffff:192.168.1.38] [twistedcaldav.memcachepool.MemCachePool#debug] Clients #free: 2, #busy: 1, #pending: 0, #queued: 0 2013-03-07 11:41:32-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Freed client: <twistedcaldav.memcachepool.PooledMemCacheProtocol instance at 0x34df5a8> 2013-03-07 11:41:32-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Clients #free: 3, #busy: 0, #pending: 0, #queued: 0 Now the second try works... 2013-03-07 11:42:57-0500 [-] [caldav-1] [HTTPChannel,25,::ffff:192.168.1.38] [twext.web2.server#info] DELETE /calendars/__uids__/admin/calendar/4BB3FD49-05EC-46FE-A958-66C790F462B9.ics HTTP/1.1 2013-03-07 11:42:57-0500 [-] [caldav-1] [HTTPChannel,25,::ffff:192.168.1.38] [twistedcaldav.directory.digest.DigestCredentialsMemcache#debug] Getting Cache Token for '23068977201759756079232744263502251584903490272716206165' 2013-03-07 11:42:57-0500 [-] [caldav-1] [HTTPChannel,25,::ffff:192.168.1.38] [twistedcaldav.memcachepool.MemCachePool#debug] Busied client: <twistedcaldav.memcachepool.PooledMemCacheProtocol instance at 0x339fdd0> 2013-03-07 11:42:57-0500 [-] [caldav-1] [HTTPChannel,25,::ffff:192.168.1.38] [twistedcaldav.memcachepool.MemCachePool#debug] Clients #free: 2, #busy: 1, #pending: 0, #queued: 0 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Freed client: <twistedcaldav.memcachepool.PooledMemCacheProtocol instance at 0x339fdd0> 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Clients #free: 3, #busy: 0, #pending: 0, #queued: 0 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.notify.Notifier#debug] Notifications are enabled: update default CalDAV|admin 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.notify.NotifierFactory#debug] Sending to notification server: update CalDAV|admin 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.notify.Notifier#debug] Notifications are enabled: update collection CalDAV|admin/calendar 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.notify.NotifierFactory#debug] Sending to notification server: update CalDAV|admin/calendar 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.cache.MemcacheChangeNotifier#debug] Changing Cache Token for '/calendars/__uids__/admin/' 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Busied client: <twistedcaldav.memcachepool.PooledMemCacheProtocol instance at 0x366ea28> 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Clients #free: 2, #busy: 1, #pending: 0, #queued: 0 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.cache.MemcacheChangeNotifier#debug] Changing Cache Token for '/calendars/__uids__/admin/calendar/' 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Busied client: <twistedcaldav.memcachepool.PooledMemCacheProtocol instance at 0x34df5a8> 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Clients #free: 1, #busy: 2, #pending: 0, #queued: 0 2013-03-07 11:42:57-0500 [-] [notifications] 2013-03-07 11:42:57-0500 [InternalNotificationProtocol,0,127.0.0.1] [twistedcaldav.notify.Coalescer#debug] Scheduling: CalDAV|admin 2013-03-07 11:42:57-0500 [-] [notifications] 2013-03-07 11:42:57-0500 [InternalNotificationProtocol,0,127.0.0.1] [twistedcaldav.notify.Coalescer#debug] Scheduling: CalDAV|admin/calendar 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Freed client: <twistedcaldav.memcachepool.PooledMemCacheProtocol instance at 0x34df5a8> 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Clients #free: 2, #busy: 1, #pending: 0, #queued: 0 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Freed client: <twistedcaldav.memcachepool.PooledMemCacheProtocol instance at 0x366ea28> 2013-03-07 11:42:57-0500 [-] [caldav-1] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Clients #free: 3, #busy: 0, #pending: 0, #queued: 0 2013-03-07 11:43:00-0500 [-] [notifications] 2013-03-07 11:43:00-0500 [-] [twistedcaldav.notify.Coalescer#debug] Time to send: CalDAV|admin 2013-03-07 11:43:00-0500 [-] [notifications] 2013-03-07 11:43:00-0500 [-] [twistedcaldav.notify.Coalescer#debug] Time to send: CalDAV|admin/calendar On 2013-03-07, at 10:34 AM, Andre LaBranche wrote: > > On Mar 7, 2013, at 6:20 AM, Robert Bruce <rbr...@celsiusinc.com> wrote: > >> ... >> Then I delete the event at 4:00 but it come right back >> >> 2013-03-06 14:53:31-0500 [-] [caldav-0] [HTTPChannel,23,24.201.74.72] >> [twext.web2.server#info] DELETE >> /calendars/__uids__/1cc63f8f-744a-4941-88c8-8ab121d03be9/calendar/D49F6977-1BCA-4EB3-A602-510B2037DC81.ics >> HTTP/1.1 >> 2013-03-06 14:53:31-0500 [-] [caldav-0] [HTTPChannel,23,24.201.74.72] >> [twext.web2.server#info] GET >> /calendars/__uids__/1cc63f8f-744a-4941-88c8-8ab121d03be9/calendar/D49F6977-1BCA-4EB3-A602-510B2037DC81.ics >> HTTP/1.1 >> 2013-03-06 14:53:31-0500 [-] [caldav-0] [HTTPChannel,24,24.201.74.72] >> [twext.web2.server#info] GET >> /calendars/__uids__/1cc63f8f-744a-4941-88c8-8ab121d03be9/calendar/D49F6977-1BCA-4EB3-A602-510B2037DC81.ics >> HTTP/1.1 > > Either the delete is failing or the GETs are failing; they can't both be > succeeding, but we can't see why. Can you turn your log level up to Debug (in > caldavd.plist) then restart the service and reproduce these steps, then reply > including the relevant portions of error.log and access.log? > > Thx, > -dre > >> >> Then I delete the event at 4:00 again and this time it is gone >> >> 2013-03-06 14:55:01-0500 [-] [caldav-0] [HTTPChannel,25,24.201.74.72] >> [twext.web2.server#info] DELETE >> /calendars/__uids__/1cc63f8f-744a-4941-88c8-8ab121d03be9/calendar/D49F6977-1BCA-4EB3-A602-510B2037DC81.ics >> HTTP/1.1 >> 2013-03-06 14:55:01-0500 [-] [caldav-0] [HTTPChannel,26,24.201.74.72] >> [twext.web2.server#info] DELETE >> /calendars/__uids__/1cc63f8f-744a-4941-88c8-8ab121d03be9/calendar/D49F6977-1BCA-4EB3-A602-510B2037DC81.ics >> HTTP/1.1 >> >> It seems to me the Following GET operations are reading back the old data? >> >> >> On 2013-03-06, at 4:31 PM, Glyph wrote: >> >>> >>> On Mar 6, 2013, at 11:57 AM, Robert Bruce <rbr...@celsiusinc.com> wrote: >>> >>>> I can't get 4.x releases to work on Ubuntu ( 12.10 in my case ) x86… and >>>> there are no packages for 4.x releases so far? relevant info is hard to >>>> find on the Net about how to set it all up. I managed to compile from >>>> SVN successfully but the logs fill with errors, >>> >>> I'm a little more interested in these errors than the ones you're having >>> with 3.2, since 4.x is a lot closer to what we're currently working on in >>> trunk. Can you send them on? Not to say that I wouldn't like you to fix >>> your current errors, but if we do find a bug and fix it, you'll still have >>> to upgrade :). >>> >>>> and after so many unpaid hours I chose 3.2 because the packages exist. >>> >>> I think that someone's working on 4.2 packages, and in fact I believe >>> they're on this mailing list. >>> >>> -glyph >>> >>> P.S.: Please remember to "reply all" so others on the list will see the >>> reply. >> >> _______________________________________________ >> 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
