Data upgrade from calendarserver 5.2.2 to 7.0 failing
Hi, While upgrading calendarserver from 5.2.2 to 7.0, I am seeing the following errors in my log file: 2016-01-19 00:45:19+0530 [-] Log opened. 2016-01-19 00:45:19+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] Beginning database schema check. 2016-01-19 00:45:19+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] Required database key VERSION: 58. 2016-01-19 00:45:19+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] Actual database key VERSION: 28. *2016-01-19 00:45:19+0530 [-] [calendarserver.tap.caldav#error] Data store not available; shutting down* 2016-01-19 00:45:19+0530 [-] [memcached-Default] Signal handled: Terminated. Any idea on why this could be happening? What information could I provide to debug this? Thanks, Rahul.
Hi Rahul, --On January 19, 2016 at 1:25:57 AM +0530 Rahul Amaram <amaramrahul@users.sourceforge.net> wrote:
While upgrading calendarserver from 5.2.2 to 7.0, I am seeing the following errors in my log file:
2016-01-19 00:45:19+0530 [-] Log opened. 2016-01-19 00:45:19+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#war n] Beginning database schema check. 2016-01-19 00:45:19+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#war n] Required database key VERSION: 58. 2016-01-19 00:45:19+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#war n] Actual database key VERSION: 28. *2016-01-19 00:45:19+0530 [-] [calendarserver.tap.caldav#error] Data store not available; shutting down* 2016-01-19 00:45:19+0530 [-] [memcached-Default] Signal handled: Terminated.
Any idea on why this could be happening? What information could I provide to debug this?
Please set the "DefaultLogLevel" key to "debug" in the plist config you are using, then try starting the server again and attach the resulting error.log file. -- Cyrus Daboo
On Tuesday 19 January 2016 10:01 PM, Cyrus Daboo wrote:
Hi Rahul,
Please set the "DefaultLogLevel" key to "debug" in the plist config you are using, then try starting the server again and attach the resulting error.log file.
I already did that but there wasn't any useful information. Anyway, here it is: 2016-01-19 22:24:38+0530 [-] Log opened. 2016-01-19 22:24:38+0530 [-] [twisted.application.app#info] twistd 15.5.0 (/usr/bin/python2.7 2.7.11) starting up. 2016-01-19 22:24:38+0530 [-] [twisted.application.app#info] reactor class: twisted.internet.epollreactor.EPollReactor. 2016-01-19 22:24:38+0530 [-] [twisted.internet.unix#info] ControlSocket starting on '/var/run/caldavd/caldavd.sock' 2016-01-19 22:24:38+0530 [-] [twisted.scripts._twistd_unix#info] set uid/gid 104/108 2016-01-19 22:24:38+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] Beginning database schema check. 2016-01-19 22:24:38+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] Required database key VERSION: 58. 2016-01-19 22:24:38+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] Actual database key VERSION: 28. 2016-01-19 22:24:38+0530 [-] [calendarserver.tap.caldav#error] Data store not available; shutting down 2016-01-19 22:24:38+0530 [-] [memcached-Default] Signal handled: Terminated. 2016-01-19 22:24:38+0530 [-] [twisted.internet.unix#info] (UNIX Port /var/run/caldavd/caldavd.sock Closed) 2016-01-19 22:24:38+0530 [-] [twisted.internet.base#info] Main loop terminated. 2016-01-19 22:24:38+0530 [-] [twisted.application.app#info] Server Shut Down. Kindly note that if I start with a fresh database with newly imported schema, it works fine. Thanks, Rahul.
On Tuesday 19 January 2016 10:26 PM, Rahul Amaram wrote:
On Tuesday 19 January 2016 10:01 PM, Cyrus Daboo wrote:
Hi Rahul,
Please set the "DefaultLogLevel" key to "debug" in the plist config you are using, then try starting the server again and attach the resulting error.log file.
I already did that but there wasn't any useful information. Anyway, here it is:
2016-01-19 22:24:38+0530 [-] Log opened. 2016-01-19 22:24:38+0530 [-] [twisted.application.app#info] twistd 15.5.0 (/usr/bin/python2.7 2.7.11) starting up. 2016-01-19 22:24:38+0530 [-] [twisted.application.app#info] reactor class: twisted.internet.epollreactor.EPollReactor. 2016-01-19 22:24:38+0530 [-] [twisted.internet.unix#info] ControlSocket starting on '/var/run/caldavd/caldavd.sock' 2016-01-19 22:24:38+0530 [-] [twisted.scripts._twistd_unix#info] set uid/gid 104/108 2016-01-19 22:24:38+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] Beginning database schema check. 2016-01-19 22:24:38+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] Required database key VERSION: 58. 2016-01-19 22:24:38+0530 [-] [txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] Actual database key VERSION: 28. 2016-01-19 22:24:38+0530 [-] [calendarserver.tap.caldav#error] Data store not available; shutting down 2016-01-19 22:24:38+0530 [-] [memcached-Default] Signal handled: Terminated. 2016-01-19 22:24:38+0530 [-] [twisted.internet.unix#info] (UNIX Port /var/run/caldavd/caldavd.sock Closed) 2016-01-19 22:24:38+0530 [-] [twisted.internet.base#info] Main loop terminated. 2016-01-19 22:24:38+0530 [-] [twisted.application.app#info] Server Shut Down.
Kindly note that if I start with a fresh database with newly imported schema, it works fine.
Thanks, Rahul.
If necessary, I can setup a public server running Debian Sid and the newly packaged calendarserver 7.0. This bug is sort of a blocker for calendarserver 7.0 debian package release. Thanks, Rahul.
Hi Rahul, --On January 20, 2016 at 3:18:10 PM +0530 Rahul Amaram <amaramrahul@users.sourceforge.net> wrote:
If necessary, I can setup a public server running Debian Sid and the newly packaged calendarserver 7.0. This bug is sort of a blocker for calendarserver 7.0 debian package release.
Have you tried running: bin/calendarserver_upgrade -- Cyrus Daboo
On Thursday 21 January 2016 02:52 AM, Cyrus Daboo wrote:
Hi Rahul,
--On January 20, 2016 at 3:18:10 PM +0530 Rahul Amaram <amaramrahul@users.sourceforge.net> wrote:
If necessary, I can setup a public server running Debian Sid and the newly packaged calendarserver 7.0. This bug is sort of a blocker for calendarserver 7.0 debian package release.
Have you tried running:
bin/calendarserver_upgrade
Hi Cyrus, I had tried this. But the command was failing. I was under the assumption that upgrade would happen automatically, so did bother to look into why this command was failing. However, a more senior Debian developer has helped me resolve this issue. Apparently, this command should be run as user "caldavd" and then it worked. He also pointed out that the accounts.xml file format for calendarserver 5.x and 7.x differ. Is there any script which will automatically convert accounts.xml file to the new format? Thanks, Rahul.
participants (2)
-
Cyrus Daboo
-
Rahul Amaram