On Jan 17, 2016, at 2:19 PM, ebach <ebach2@gmail.com> wrote:
Does anything show up in the various log files calendarserver outputs too?
Nope. access.log shows only the server starting up (and, when I hit ^C, shuttung down): Log opened - server start: [Sun Jan 17 14:16:53 2016]. Log closed - server stop: [Sun Jan 17 14:18:35 2016]. error.log shows nothing. A little more playing around (adding debug messages in appropriate-looking places), it seems that it gets as far as running UpgradeReleaseLockStep (in txdav.common.datastore.upgrade.sql.upgrade). But no further than that.
On Jan 17, 2016, at 12:49 AM, Jacques Distler <distler@golem.ph.utexas.edu> wrote:
On Jan 17, 2016, at 12:52 AM, Jacques Distler <distler@golem.ph.utexas.edu> wrote:
bin/calendarserver_upgrade
completed without errors. But
bin/run -n
stalls at
2016-01-17 00:26:57-0600 [-] [twistedcaldav.upgrade#warn] Migrating delegates to the store
How can I diagnose what's causing the problem? After hitting ^C (the only way to get out), the old
proxies.sqlite
file is deleted (I can easily restore a copy from backup), but nothing seems to get me any further in the process of initializing the server.
N.B.: The "delegates" and "delegate_groups" tables in postgreSQL both still have zero rows, so none of the delegate data actually got migrated.