On Nov 16, 2015, at 4:17 AM, Frank Fechner wrote: > Hi, > > had this exact same error too. It comes if you don’t use a database as > backend (default config) but didn’t deactivate it (which is NOT in default > example config). > > Simply add the following lines to your caldavd.plist > > <key>UseDatabase</key> > <false/> > > Hope this helps.
Thanks for the clue! However, the Debian package is configured to use postgresql by default. But I think based on what you're saying that there may be a communication issue between the database and caldavd. Postgresql is so obtuse to configure for "peer" versus password authentication, I may have screwed something up when I attempted to delete and recreate the database. ./k > >> Am 13.11.2015 um 19:54 schrieb Kyle Silfer <k...@rtoads.com>: >> >> I've installed the latest Debian calendarserver package on Ubuntu 14.04 on 3 >> different more-or-less identical Dell servers. >> >> On one of the 3 servers I am experiencing an error. It started when I >> imported calendar events from a particularly large calendar. The symptom on >> the client side is a "CalDAVAccountRefreshQueueableOperation" error. It >> occurs now with every attempt to connect to the account. >> >> The symptom on the server side is: >> >> 2015-11-13 09:21:33-0700 [-] [caldav-0] File >> "/usr/lib/python2.7/dist-packages/txdav/common/datastore/sql.py", line 1570, >> in initFromStore >> 2015-11-13 09:21:33-0700 [-] [caldav-0] self._txn, >> resourceID=self._resourceID))[0] >> 2015-11-13 09:21:33-0700 [-] [caldav-0] exceptions.IndexError: list >> index out of range >> >> Thinking this to perhaps be due to corrupt data, I deleted the caldav >> database plus files in the /var/spool/caldavd and /var/lib/caldavd, >> restarted the server and am still getting that error each time I try to >> connect. >> >> The error seems to be from Python and has come up for users of other >> packages too. >> >> If it isn't the calendar data that is causing or contributing to this error, >> is there a Python cache or other persistent data that needs to be deleted to >> really have a fresh start with calendarserver? >> >> Because my other two installs are working fine, including one where I >> imported the same data. >> >> Any clues? >> >> ./k >> >> >> _______________________________________________ >> calendarserver-users mailing list >> calendarserver-users@lists.macosforge.org >> https://lists.macosforge.org/mailman/listinfo/calendarserver-users > > > -- Kyle Silfer Reign of Toads IT Consultation Services 505.265.5840 h 505.918.0978 c 505.346.0660 x242 w _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-users
