I have DHIS2.33.9 and an error for upgrade into 2.34.0/2.34.1

upgradeLog.docx (42.6 KB)
flyway.xls (74 KB)
Good day everyone,
I am trying to upgrade from 2.33.9 to 2.34.0 which failed and I tried 2.34.1 which also failed. I can’t vividly understand the error and I need technical support. Please attach the logs in a word document because of the size of the records and the flyway database query.

These are the major ERRORS within the log file… Why is my log showing dhis.log and Appender? How do they stop some of the listeners?

Sep 28 03:05:50 hmis tomcat9[17477]: 2022-09-28 03:05:50,760 main ERROR Unable to create file dhis.log java.io.IOException: Permission denied

Sep 28 03:05:50 hmis tomcat9[17477]: 2022-09-28 03:05:50,768 main ERROR Unable to invoke factory method in class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile: java.lang.IllegalStateException: No factory method found for class org.apache.logging.log4j.core.appender.RollingFileAppender java.lang.IllegalStateException: No factory method found for class org.apache.logging.log4j.core.appender.RollingFileAppender

Sep 28 03:06:00 hmis tomcat9[17477]: 2022-09-28 03:06:00,948 main ERROR Unable to create file dhis.log java.io.IOException: Permission denied

Sep 28 03:06:00 hmis tomcat9[17477]: 2022-09-28 03:06:00,953 main ERROR Could not create plugin of type class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile: java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@40343761] unable to create manager for [dhis.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@13a6a87f[pattern=dhis.log%i, append=true, bufferedIO=true, bufferSize=8192, policy=CompositeTriggeringPolicy(policies=[SizeBasedTriggeringPolicy(size=26214400)]), strategy=DefaultRolloverStrategy(min=1, max=3, useMax=true), advertiseURI=null, layout=* %-5p %d{ISO8601} %m (%F [%t])%n %X{sessionId}, filePermissions=null, fileOwner=null]] java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@40343761] unable to create manager for [dhis.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@13a6a87f[pattern=dhis.log%i, append=true, bufferedIO=true, bufferSize=8192, policy=CompositeTriggeringPolicy(policies=[SizeBasedTriggeringPolicy(size=26214400)]), strategy=DefaultRolloverStrategy(min=1, max=3, useMax=true), advertiseURI=null, layout=* %-5p %d{ISO8601} %m (%F [%t])%n %X{sessionId}, filePermissions=null, fileOwner=null]]

Sep 28 03:06:00 hmis tomcat9[17477]: 2022-09-28 03:06:00,956 main ERROR Unable to invoke factory method in class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile: java.lang.IllegalStateException: No factory method found for class org.apache.logging.log4j.core.appender.RollingFileAppender java.lang.IllegalStateException: No factory method found for class org.apache.logging.log4j.core.appender.RollingFileAppender
Sep 28 03:06:00 hmis tomcat9[17477]: 2022-09-28 03:06:00,962 main ERROR Null object returned for RollingFile in Appenders.

Dear all,
Since I cannot identify why the migration from 2.33.9 to 2.34.1 failed, nor did I receive any response(s), I upgraded from 2.33.9 to 2.35.14, and it was successful.
Then I upgrade my java to OpenJDK-11 as per upgrade reviews and upgrade, from 2.35.14 to 2.38.1.1. These steps fixed my issues
I will still appreciate it if someone can tell me why the upgrade from 2.33.9 to 2.34.1 failed

Hi Gerald Thomas,

From the details of the log file you shared, it looks like there was a permission issue. It is possible that the tomcat user didn’t have sufficient permissions in the dhis2 home directory.

I hope our response is able to solve the issue you were facing.

With :heavy_heart_exclamation: from the Dhistance Team.

DHISTANCE.com: The Easiest DHIS2 Setup. Up and running in 5 minutes!

No technical knowledge needed! Great Support with Data Security/Confidentiality.