Calendar hang for one user

Thanks, but unfortunately this doesn't help.

Calendar won't connect to the user's calendar. You get nothing, for a while, no calendar to export or delete...it just sits there, and eventually times out. So you can't create a new calendar, you can't export the old, you can't access the calendar to start cleaning out. 😟

Thanks Linc. No, that doesn't work either. Can try and connect to the calendar from a completely new machine, and it still hangs and times out. Unfortunately.

I think it needs some way to clear the calendar from the server. It might require a command-line operation. I think in Server 4 they now store calendars in a database, rather than filesystem, so I can't just go and delete files by the looks of it. I'm hoping someone on the Calendar Server team might have more idea and can help?

Appreciate all the ideas to try though Linc.

Well, I'm hoping there is some other option. To do this will probably cause upper management to tell me to scrap OS X server and get Exchange. Also, I have no reason for how this happened, so what if it happens again?

Ok, one of the Software Engineers at Apple sent me the solution (I don't know if he wants me to put his name here, so I won't). Anyway, he told me to basically do:

You can nuke a user and all that user's calendars and events using the calendarserver_purge_principals tool.

Something like this:

sudo calendarserver_purge_principals -v user01

Keep in mind that calendar data often belongs to more than one user. For example, running the above commands will delete not only user01's calendars, but also any events that user01 has created which others may be attending. Other attendees will see cancellation notices for those events.

Now, we wanted to avoid the notification spams, so we came up with a much hackier solution, that ends up doing what was suggested, after some manual cleanup, to avoid the notifications going out.

What we discovered is that we were able to delete the events directly from the calendar database, which DID NOT send any cancellation notices to anybody, but didn’t seem to completely clean up the calendars either. However, we then discovered that running the ‘purge’ command after manually deleting the events finished the clean up, and did not trigger any cancellation notices either!

So the steps to fix it were:

1. Get the list of users and their UUIDs to find the one you want to delete:

sudo calendarserver_manage_principals --list-principals users

2. Connect to the calendar server database (as root):

psql -h /var/run/caldavd/PostgresSocket -U caldav caldav

3. Run this query, substituting the UUID:

DELETE FROM calendar_object

WHERE calendar_object.calendar_resource_id IN (

SELECT calendar_bind.calendar_resource_id

FROM

calendar_bind

JOIN calendar_home ON calendar_home.resource_id = calendar_bind.calendar_home_resource_id

WHERE calendar_home.owner_uid = '556D3E30-6FF9-4681-9985-78F192BD591A'

);

4. Run the purge command, substituting the UUID:

sudo calendarserver_purge_principals -v 556D3E30-6FF9-4681-9985-78F192BD591A

This leaves you without a calendar, so you have to then create a new one, or get someone to invite you to an event, so the system creates one for you.

And hopefully this comes in handy for someone looking for a solution for a similar problem.