Hey everybody We migrated people to our DCS implementation and ran into an issue where some people's calendars were accessible as subscriptions just fine, but others you could authenticate (authenticated:read ACL) but it just timed out. We had advised people to migrate their old calendars over by exporting as an .ics then reimporting it and assigning the events to their calendar in DCS. The people who's calendars are at issue/time out appear to have done this, as they have hundreds of sequential PUT's in the access logs. About 3 a second. So, I have to see if this is the problem. My plan is to have a user with a large calendar who didn't do this yet and who's calendar I can access attempt this, and then see if my access to their calendar breaks. My big question is: How can I revert people's calendars/users to a state where they're accessible or 'fresh' if my theory is correct? I don't want to irreparably break my test subjects account and if I'm right, I want to fix the users who are having problems. Is it as simple as commenting them out of accounts.xml, waiting 10 minutes then uncommenting them? Do I have to do some gnarly SQL-Fu? And worst case scenario; can I simply blow away the whole database, restart caldavd, redo my acl/proxy stuff in the command line client and be merrily on my way? Cheers, tack
Hi tack, --On June 23, 2008 11:12:56 AM -0700 tack <tack@tractionco.com> wrote:
My big question is: How can I revert people's calendars/users to a state where they're accessible or 'fresh' if my theory is correct? I don't want to irreparably break my test subjects account and if I'm right, I want to fix the users who are having problems. Is it as simple as commenting them out of accounts.xml, waiting 10 minutes then uncommenting them? Do I have to do some gnarly SQL-Fu? And worst case scenario; can I simply blow away the whole database, restart caldavd, redo my acl/proxy stuff in the command line client and be merrily on my way?
If you don't care about existing data, simple option would be to delete the entire calendar imported into and create a new one. -- Cyrus Daboo
Thanks Cyrus. Would I do this by rm/mkdir in the client tool or something similar? I couldn't find where this was on the regular command line. Cheers, tack On Jun 23, 2008, at 11:39 AM, Cyrus Daboo wrote:
Hi tack,
--On June 23, 2008 11:12:56 AM -0700 tack <tack@tractionco.com> wrote:
My big question is: How can I revert people's calendars/users to a state where they're accessible or 'fresh' if my theory is correct? I don't want to irreparably break my test subjects account and if I'm right, I want to fix the users who are having problems. Is it as simple as commenting them out of accounts.xml, waiting 10 minutes then uncommenting them? Do I have to do some gnarly SQL-Fu? And worst case scenario; can I simply blow away the whole database, restart caldavd, redo my acl/proxy stuff in the command line client and be merrily on my way?
If you don't care about existing data, simple option would be to delete the entire calendar imported into and create a new one.
-- Cyrus Daboo
Hi tack, --On June 23, 2008 12:09:26 PM -0700 tack <tack@tractionco.com> wrote:
Thanks Cyrus.
Would I do this by rm/mkdir in the client tool or something similar? I couldn't find where this was on the regular command line.
Simple option is to just delete the file on disk and restart the calendar server. -- Cyrus Daboo
I'm thinking also that maybe nothing is wrong server-side. It's just that the first time you try to subscribe to this huge calendar, it takes longer than iCal's 30 second timeout will allow. I found this and similar on google: http://forums.macosxhints.com/showthread.php?t=86251 We tried subscribing using Lightning and it took 2 minutes, but it worked. So I think there could be something to this. So... I know it's more of a client side question, but anybody know how to increase iCal's timeout interval? I couldn't find it in the plist or in defaults read com.apple.iCal. And I didn't find it in the application bundle, but haven't opened anything in resource or hex editors. I'd like to try this before I delete anybodies calendar data. Cheers, tack On Jun 23, 2008, at 11:39 AM, Cyrus Daboo wrote:
Hi tack,
--On June 23, 2008 11:12:56 AM -0700 tack <tack@tractionco.com> wrote:
My big question is: How can I revert people's calendars/users to a state where they're accessible or 'fresh' if my theory is correct? I don't want to irreparably break my test subjects account and if I'm right, I want to fix the users who are having problems. Is it as simple as commenting them out of accounts.xml, waiting 10 minutes then uncommenting them? Do I have to do some gnarly SQL-Fu? And worst case scenario; can I simply blow away the whole database, restart caldavd, redo my acl/proxy stuff in the command line client and be merrily on my way?
If you don't care about existing data, simple option would be to delete the entire calendar imported into and create a new one.
-- Cyrus Daboo
participants (2)
-
Cyrus Daboo
-
tack