I upgraded my Jamf Pro server from 10.28.to 10.31 today (it runs on Windows server). Based on the instructions about the upgrade I checked the Change Management log file path and 1) it exists and 2) Tomcat runs as Local Service and has permissions to the directory. I also tried changing the permissions on the directory so 'everyone' has modify. I rebooted the server. That didn't make any difference.
Since running the 10.31 upgrade, the server startup will not get past Initializing Change Management. I am wondering if anyone else has encountered this and what a solution might be. I did submit a support request with Jamf but have not heard back yet.
Solved! Go to Solution.
I did a restore of our server back to 10.28 version. Then I updated to 10.29.2. After that I updated to 10.31. I still got the hang on Initializing Change Management. Jamf support had me do the following which fixed the issue:
1. Stop Tomcat
2. Run the following query in MySQL: truncate change_management; (you may first need to run the command 'use jamfsoftware;'
3. Start Tomcat
4. Once Jamf Pro is initialized, re-enable 'Use Log File' and 'Use Syslog Server' if needed and modify the Change Management log file location within Settings > System Settings > Change Management to the correct location