Tag Archives: 500 error

Mac Server Update Breaks Profile Manager

Profile Manager 3.2.1 Error – Symptoms

With the recent “Shellshock” exploit floating around, I just went through my servers to get them all up to date. I updated my Mac OS X Mavericks Server to Server.app 3.2.1. In doing this update – it actually broke my profile manager with an error:

We're sorry, but something went wrong. We've been notified about this issue and we'll take a look at it shortly.
We’re sorry, but something went wrong. We’ve been notified about this issue and we’ll take a look at it shortly.

I also received other errors with Profile Manager:
syntaxerror json parse error unrecognized token '>' ok profile manager
Profile manager 3.2.1 was also giving 500 Server errors and in general just would work. I could get to the login screen – but was unable to actually log in. It would redirect to the above error page. More or less, profile manager was completely broken – and I didn’t have a backup to restore to.

After some digging around – it appears that something goes haywire in the upgrade process.  (Like you didn’t already know that! :D)

Profile Manager 3.2.1 Error – The Fix

If you are having the same problems as I posted above, all you need to do to fix Profile Manager 3.2.1 errors is the following.

  1. Run the command:
    sudo psql -U _devicemgr -d devicemgr_v2m0 -h /Library/Server/ProfileManager/Config/var/PostgreSQL -c "UPDATE auto_join_profiles SET usage_log = NULL"
  2. Run the command:
    sudo /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/config/migrateDB

The first command clears out the usage log in the PostgreSQL database. All I can figure is there is something in that Log that the migrateDB command does not like. Once you reset that log – you are then able to successfully migrate the database. You may get one more error page – but just hit the reload button and it will actually load the page after.