Server 3.2.1 (10.9.5) – Postgres won't start

Question

After upgrading from Server 3.1.2 (Mavericks 10.9.3) to Server 3.2.1 (Mavericks 10.9.5), I cannot start Postgres:
# serveradmin start postgres
postgres:error = "CANNOT_START_SERVICE_TIMEOUT_ERR"
Here is what I see in system.log:
Sep 18 18:36:20 server com.apple.serverd[78]: ERROR: SMJobSubmit: The operation couldn’t be completed. (kSMErrorDomainLaunchd error 9 - The job dictionary specifies that it is disabled.)
Sep 18 18:36:20 server serveradmin[2249]: servermgr_postgres: waiting for postgres to respond
Sep 18 18:36:24 server serveradmin[2249]: servermgr_postgres: Timed out trying to start postgres.
Sep 18 18:36:24 server serveradmin[2249]: posting dist not
Not sure what to do from here. Postgres was running fine under 10.9.3.
Rusty

Answer 1

Ok making progress here, but the utf8 options seems to be causing some issue...
sh-3.2# chown -R _postgres:_postgres /Library/Server/PostgreSQL
sh-3.2# cd /Library/Server/PostgreSQL
sh-3.2# sudo -u _postgres /Applications/Server.app/Contents/ServerRoot/usr/bin/initdb /Library/Server/PostgreSQL/Data -E utf8
The files belonging to this database system will be owned by user "_postgres".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.UTF-8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /Library/Server/PostgreSQL/Data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
creating configuration files ... ok
creating template1 database in /Library/Server/PostgreSQL/Data/base/1 ... ok
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating collations ... ok
creating conversions ... ok
creating dictionaries ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
loading PL/pgSQL server-side language ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok
syncing data to disk ... ok
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
Success. Since you appear to be using the default database,
the system-wide instance of postgres will be launched on-demand by
the various services which use it.
If necessary, you can now start the database server using:
    serveradmin start postgres
See webappctl(8) to learn how to launch postgres on-demand for
sh-3.2#  mv /Volumes/TinTin/Applications/Server.app/Contents/ServerRoot/usr/bin/postgres /Volumes/TinTin/Applications/Server.app/Contents/ServerRoot/usr/bin/postgres_of f
sh-3.2# mv /Volumes/TinTin/Applications/Server.app/Contents/ServerRoot/usr/bin/postgres_re al /Volumes/TinTin/Applications/Server.app/Contents/ServerRoot/usr/bin/postgres
sh-3.2# sudo -u _postgres /Applications/Server.app/Contents/ServerRoot/usr/bin/pg_upgrade -b /Volumes/TinTin/Applications/Server.app/Contents/ServerRoot/usr/bin -B /Applications/Server.app/Contents/ServerRoot/usr/bin -d /Library/Server/PostgreSQL/DataOld -D /Library/Server/PostgreSQL/Data
Performing Consistency Checks
Checking cluster versions                                   ok
Checking database user is a superuser                       ok
Checking for prepared transactions                          ok
Checking for reg* system OID user data types                ok
Checking for contrib/isn with bigint-passing mismatch       ok
Creating dump of global objects                             ok
Creating dump of database schemas
                                                            ok
lc_collate cluster values do not match:  old "C", new "en_US.UTF-8"
Failure, exiting