After upgrading to the new Server 2.2 app today, I received the following warning once the upgrade process had completed:
An error occurred while updating your service data.
Services may not function as expected
The, opening the Server app, I received the following warning:
An error occurred on the server while reading settings.
The error occurred while reading settings for the Profile Manager service.
And in Console I find the following error (not exactly sure which ones to look for) in the profilemangager.log:
Dec 7 10:12:40 rocking-mm.com ProfileManager <Info>: ServermgrDevicemgr starting...
Dec 7 10:12:40 rocking-mm.com ProfileManager <Info>: default_profile_created_at_least_once was already true
Dec 7 10:12:40 rocking-mm.com ProfileManager <Warning>: ** has_many_polymorphs: Warning; not all usage scenarios for polymorphic scopes are supported yet.
Dec 7 10:12:40 rocking-mm.com ProfileManager <Info>: ServermgrDevicemgr done!
I have also seen other errors aluding to postgres not being available.
Has anyone experienced similar problems when upgrading to 2.2? I'm getting sick of OS X Server ever since Lion. Snow Leopard Server wasn't perfect, but allowed for much more control to correct problems.
I want to second what Joel said. On Server App 2.1 I was running Postrgres App 1.0 which was running on port 5432. Prior to Server App 2.2 I don't think that OS X Server was listening on port 5432, but instead used the socket to let the services connect directly to the database. It seems that Server App 2.2 has changed that now and actually works on port 5432, thus the upgrade process would have conflicted with the running instance of Postgres on port 5432.
I have restored from a time machine backup, turned off the 3rd party Postgres instance, performed the upgrade, then installed the 3rd party Postgres instance to run on port 5433. Everything is working perfectly now. I have been running successfully now for 3 days without incident -- sorry for it posting this solution sooner, I just didn't have the time.