Update 2021-09-22: Please check my other thread for the solution: https://community.jamf.com/t5/jamf-pro/upgrade-stuck-at-initializing-change-management/td-p/244134. This thread was stuck in admin approval and got released later.
I upgraded tonight from 10.30.0 to 10.31.1 and it freezes at Initializing Change Management. I'm running on CentOS 7. I have not restarted any services or rebooted yet. I use jamfproinstaller.run like always. Everything went normal at the terminal – no errors.
I checked the /usr/local/jss/logs/JAMFSoftwareServer.log and there is this one error:
2021-08-11 19:26:00,457 7ERROR] ]erverThread] ]gUncaughtExceptionHandler] - Uncaught Exception from thread InitializeServerThread - ManagerFactory yorg.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@6bfb2009] unable to create manager for [/var/log/JAMFChangeManagement.log] with data aorg.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@5330f4393pattern=/var/log/JAMFChangeManagement.log.%i, append=true, bufferedIO=true, bufferSize=8192, policy=SizeBasedTriggeringPolicy(size=10485760), strategy=DefaultRolloverStrategy(min=1, max=7, useMax=true), advertiseURI=null, layout=%m%n, filePermissions=null, fileOwner=null]]
java.lang.IllegalStateException: ManagerFactory yorg.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@6bfb2009] unable to create manager for [/var/log/JAMFChangeManagement.log] with data aorg.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@5330f4393pattern=/var/log/JAMFChangeManagement.log.%i, append=true, bufferedIO=true, bufferSize=8192, policy=SizeBasedTriggeringPolicy(size=10485760), strategy=DefaultRolloverStrategy(min=1, max=7, useMax=true), advertiseURI=null, layout=%m%n, filePermissions=null, fileOwner=null]]
at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:115) ~ log4j-core-2.13.3.jar:2.13.3]
at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100) ~ log4j-core-2.13.3.jar:2.13.3]
at org.apache.logging.log4j.core.appender.rolling.RollingFileManager.getFileManager(RollingFileManager.java:205) ~ log4j-core-2.13.3.jar:2.13.3]
at org.apache.logging.log4j.core.appender.RollingFileAppender$Builder.build(RollingFileAppender.java:146) ~ log4j-core-2.13.3.jar:2.13.3]
at com.jamfsoftware.logging.change.impl.ChangeManagementConfigurationServiceImpl.createRollingFileAppender(ChangeManagementConfigurationServiceImpl.java:235) ~ change-management-impl-10.31.1-t1628520988.jar:?]
at com.jamfsoftware.logging.change.impl.ChangeManagementConfigurationServiceImpl.reset(ChangeManagementConfigurationServiceImpl.java:157) ~ change-management-impl-10.31.1-t1628520988.jar:?]
at com.jamfsoftware.jss.server.initialization.InitializeServerThread.run(InitializeServerThread.java:534) ~ classes/:?]
at org.springframework.security.concurrent.DelegatingSecurityContextRunnable.run(DelegatingSecurityContextRunnable.java:84) ~ spring-security-core-5.3.3.RELEASE.jar:5.3.3.RELEASE]
at java.lang.Thread.run(Thread.java:829) )?:?]
Any ideas on what to do next?