Failed to upgrade to build 5300/5301

Failed to upgrade to build 5300/5301

Issue: Upgrade fails while attempting to upgrade to the build 5300/5301.

Cause: Upgrade fails due to a necessary system property required for logging slow queries is missing.

This issue will arise while attempting to upgrade to the 5300/5301(Mandatory build) because of the changes made on the code level.

Trace:

Caused by: java.lang.Error: com.zoho.logs.common.config.ConfigException:L100:ERROR: Mandatory file (logging.properties) to use logagent is not defined. Please configure logging.properties in WEB-INF/classes dir (if SAS build) or in JVM args. For more details, please refer https://learn.zoho.com/portal/zohocorp/knowledge/manual/logagent/article/logging-properties


Solution: 
  • Restore the Analytics Plus backup
  • Open the "UpdateManager.sh(Linux) or UpdateManager.bat"(Windows) under following location <AnalyticsPlus>/bin and update the below property accordingly.

For linux

Actual Entry:

$JAVA -Xmx1024m  $JAVA_OPTS -DisPostgreBuild=true -Dtier-type=BE -Djava.library.path=./lib/native -Dtools.discSpaceCheck=false -Dtier-id=BE1 -cp $CLASSPATH com.adventnet.tools.update.installer.UpdateManager -u conf $*
Modified Entry:
$JAVA -Xmx1024m  $JAVA_OPTS -DisPostgreBuild=true -Dtier-type=BE -Djava.library.path=./lib/native -Dtools.discSpaceCheck=false -Dtier-id=BE1 -Djava.util.logging.config.file=./conf/logging.properties -cp $CLASSPATH com.adventnet.tools.update.installer.UpdateManager -u conf $*

For Windows 

Actual Entry:

"%JAVA_HOME%\bin\java" -Xmx1024m  %JAVA_OPTS% -DisPostgreBuild=true -Dtier-type=BE -Djava.library.path=.\lib\native -Dtools.discSpaceCheck=false -Dtier-id=BE1 com.adventnet.tools.update.installer.UpdateManager -u conf %*
Modified Entry:
"%JAVA_HOME%\bin\java" -Xmx1024m  %JAVA_OPTS% -DisPostgreBuild=true -Dtier-type=BE -Djava.library.path=.\lib\native -Dtools.discSpaceCheck=false -Dtier-id=BE1 -Djava.util.logging.config.file=./conf/logging.properties com.adventnet.tools.update.installer.UpdateManager -u conf %*

  1. Save the changes and proceed to upgrade.

Note:
This issue will be fixed from the version 5330