You missed a very important point from release notes:
Direct upgrades from Jamf Pro 10.28.x or earlier to Jamf Pro 10.30.0 or later may fail. An incremental upgrade to 10.29.x is now required for upgrades from 10.28.0 or earlier to Jamf Pro 10.30.0 or later.
You missed a very important point from release notes:
Direct upgrades from Jamf Pro 10.28.x or earlier to Jamf Pro 10.30.0 or later may fail. An incremental upgrade to 10.29.x is now required for upgrades from 10.28.0 or earlier to Jamf Pro 10.30.0 or later.
I wonder why that data was not presented in the same list as the three other warnings. I didn't know this, thank you for pointing it out.
It's not listed in the known issues either. Shouldn't it be?
https://account.jamf.com/products/jamf-pro/known-issues
It's not listed in the known issues either. Shouldn't it be?
https://account.jamf.com/products/jamf-pro/known-issues
@Samstar777 Can you tell me where this text appears? I cannot find it in the release notes.
@Samstar777 Can you tell me where this text appears? I cannot find it in the release notes.
You may check the same in below link from Jamf
https://docs.jamf.com/10.31.0/jamf-pro/release-notes/Important_Notices.html
This failed for me tonight going from 10.30.1 to 10.31.
This failed for me tonight going from 10.30.1 to 10.31.
NOTE: This had to do with ChangeManagement resetting the log4j2 properties file to the defaulted JAMF PRO install directories. If you set it to anything else, you will have to modify it before starting tomcat after upgrade to 10.31.
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
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
Literally just ran into same problem as you aamjohns going to 10.31.1 and those instructions worked for my Windows server box. Thanks!
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
This was so helpful, thank you!
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
@aamjohns thank you. This worked for us as well. We had engaged support and they gave us another suggestion that didn't help, but this worked like a charm.
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
This worked! thank You!
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
Just encountered this issue upgrading from 10.30.2 to 10.32.2, the truncate command fixed it right up, thank you.
Thanks for this info - this worked for us on windows going from 10.29.2 to 10.33
