Caldavd failing to start after upgrade to Server 3.2.1

Question

This problem, caldavd not starting after upgrading to Server 3.2.1, is a variation on the theme of PostgresQL not starting.  It too boils down to a postgres database not having been updated properly.  Below are the steps needed to fix this problem:
sudo su -
# Change to the directory with the postgres database for the calendars and contacts
cd /Library/Server/Calendar\ and\ Contacts/Data/Database.xpg
# Disable caldavd for now
launchctl unload -w /Applications/Server.app/Contents/ServerRoot/System/Library/LaunchDaemons/org.c alendarserver.calendarserver.plist
# move the broken database out of the way and build a new empty one
mv cluster.pg broken-cluster.pg
mkdir cluster.pg && chmod 700 cluster.pg && chown _calendar:_calendar cluster.pg
sudo -u _calendar /Applications/Server.app/Contents/ServerRoot/usr/bin/initdb "/Library/Server/Calendar and Contacts/Data/Database.xpg/cluster.pg" -E utf8 --lc-ctype=C
# Finish the upgrade job that never completed by explicitly invoking the previous version of postgres:
sudo -u _calendar /Applications/Server.app/Contents/ServerRoot/usr/bin/pg_upgrade -b /Applications/Server.app/Contents/ServerRoot/usr/libexec/postgresql9.2 -B /Applications/Server.app/Contents/ServerRoot/usr/bin -d /Library/Server/Calendar\ and\ Contacts/Data/Database.xpg/cluster.pg.original_for_upgrade/ -D /Library/Server/Calendar\ and\ Contacts/Data/Database.xpg/cluster.pg
# Mark the newly upgraded database as no longer in need of an upgrade
sudo -u _calendar touch cluster.pg/.NoRestoreNeeded
# Start caldavd back up
launchctl load -w /Applications/Server.app/Contents/ServerRoot/System/Library/LaunchDaemons/org.c alendarserver.calendarserver.plist
And everything should be the way it should have been in the first place!

Answer 1

Hi, I have the same issue and Linc Davis pointed me to this thread from Re: Server Calendar migration failed.
Your solution already got me somewhere, so thanks for that
I need to note that my machine is on Yosemite (10.10.1) and I'm running Server 4.
The only issue I have is that I get an error message when running pg_upgrade, the log says:
  pg_upgrade run on Fri Jan 23 09:31:30 2015
command: "/Applications/Server.app/Contents/ServerRoot/usr/libexec/postgresql9.2/pg_ctl" -w -l "pg_upgrade_server.log" -D "/Library/Server/Calendar and Contacts/Data/Database.xpg/b$
waiting for server to start....LOG:  database system was interrupted; last known up at 2013-11-02 12:21:52 CET
LOG:  creating missing WAL directory "pg_xlog/archive_status"
LOG:  starting archive recovery
LOG:  restored log file "000000010000000000000002" from archive
LOG:  invalid magic number D075 in log file 0, segment 2, offset 0
LOG:  invalid checkpoint record
FATAL:  could not locate required checkpoint record
HINT:  If you are not restoring from a backup, try removing the file "/Library/Server/Calendar and Contacts/Data/Database.xpg/broken-cluster.pg/backup_label".
LOG:  startup process (PID 12315) exited with exit code 1
LOG:  aborting startup due to startup process failure
........................................................... stopped waiting
pg_ctl: could not start server
Examine the log output.
The log talks about removing the backup_label file. When I do that the log says the following:
  pg_upgrade run on Fri Jan 23 09:41:34 2015
command: "/Applications/Server.app/Contents/ServerRoot/usr/libexec/postgresql9.2/pg_ctl" -w -l "pg_upgrade_server.log" -D "/Library/Server/Calendar and Contacts/Data/Database.xpg/b$
waiting for server to start....LOG:  database system was interrupted; last known up at 2013-11-02 12:21:52 CET
LOG:  starting archive recovery
LOG:  invalid magic number D075 in log file 0, segment 2, offset 0
LOG:  invalid primary checkpoint record
LOG:  could not open file "pg_xlog/000000010000000000000001" (log file 0, segment 1): No such file or directory
LOG:  invalid secondary checkpoint record
PANIC:  could not locate a valid checkpoint record
FATAL:  the database system is starting up
.LOG:  startup process (PID 15068) was terminated by signal 6: Abort trap
LOG:  aborting startup due to startup process failure
stopped waiting
pg_ctl: could not start server
Examine the log output.
Thanks already for the help