Skip to main content
Solved

Jamf server hanging on 'Initializing Change Management'

  • August 3, 2021
  • 15 replies
  • 100 views
A
Forum|alt.badge.img+10

Hello,

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.

Thank you,

AJ

Best answer by Samstar777

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.

    15 replies

    Samstar777
    Forum|alt.badge.img+11
    • Samstar777
    • Valued Contributor
    • Answer
    • August 4, 2021

    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.

    A
    Forum|alt.badge.img+10
    • aamjohns
    • Author
    • Valued Contributor
    • August 4, 2021

    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.

    A
    Forum|alt.badge.img+10
    • aamjohns
    • Author
    • Valued Contributor
    • August 4, 2021

    It's not listed in the known issues either.  Shouldn't it be?

    https://account.jamf.com/products/jamf-pro/known-issues

    A
    Forum|alt.badge.img+10
    • aamjohns
    • Author
    • Valued Contributor
    • August 4, 2021

    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
    Forum|alt.badge.img+11
    • Samstar777
    • Valued Contributor
    • August 4, 2021

    @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

     

    A
    Forum|alt.badge.img+10
    • aamjohns
    • Author
    • Valued Contributor
    • August 4, 2021

    10-4 I see it.

     

    M
    Forum|alt.badge.img+2
    • man6
    • New Contributor
    • August 14, 2021

    This failed for me tonight going from 10.30.1 to 10.31.

    M
    Forum|alt.badge.img+2
    • man6
    • New Contributor
    • August 14, 2021

    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.

    A
    Forum|alt.badge.img+10
    • aamjohns
    • Author
    • Valued Contributor
    • August 14, 2021

    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

    AJPinto
    J
    DMac
    J
    Forum|alt.badge.img+4
    • jurbina23
    • New Contributor
    • August 25, 2021

    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!

    llullo1
    Forum|alt.badge.img+3
    • llullo1
    • New Contributor
    • September 13, 2021

    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! 

     

    J
    Forum|alt.badge.img+1
    • jstasik
    • New Contributor
    • September 15, 2021

    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.

    J
    Forum|alt.badge.img
    • jfitzemeyer
    • New Contributor
    • September 18, 2021

    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!

     

    S
    Forum|alt.badge.img
    • SecurAP
    • New Contributor
    • September 28, 2021

    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.

    J
    W
    Forum|alt.badge.img
    • wam
    • New Contributor
    • November 3, 2021

    Thanks for this info - this worked for us on windows going from 10.29.2 to 10.33

    J
    Terms & ConditionsCookie settingsAccessibility statement