Jasperserver 7.5 to 8.0 Upgrade- Build Failed - Weak Password

[kevin.boerboom]

Hello - 

We are upgrading jasper server from 7.5.0 to 8.0.0 by following the following document:  https://docs.tibco.com/pub/js-jrs-ce/8.0.0/doc/pdf/TIB_js-jrs-ce_8.0.0_Upgrade-Guide.pdf?id=2

 

Upgrade commands (used after necessary backup and setup steps):

cd /tmp/jasper-8.0/jasperreports-server-cp-8.0.0-bin/buildomatic/ 

./js-upgrade-newdb-ce.sh /tmp/backup-7.5/js-7.5-export.zip

 

The above upgrade script fails with the below error:

import-upgrade-ce:
     [echo]  --- (import-export.xml:run-import-export) archiveArg = --input-zip=/tmp/backup-7.5/js-7.5-export.zip --- 
     [echo]              dbType = postgresql
     [echo]             jdbcJar = postgresql-42.2.20.jar
     [echo]         currentConf = /tmp/jasper-8.0/jasperreports-server-cp-8.0.0-bin/buildomatic/build_conf/default
     [echo]  importExportConfig = /tmp/jasper-8.0/jasperreports-server-cp-8.0.0-bin/buildomatic/conf_source/ieCe
     [echo]  
     [echo] Validating JasperServer database connection at jdbc:postgresql://localhost:5432/jasperserver. Phase: [import-export-test]
[advanced-sql] Executing commands
[advanced-sql] 1 of 1 SQL statements executed successfully
     [echo] Connection OK
     [java] First resource path: /tmp/jasper-8.0/jasperreports-server-cp-8.0.0-bin/buildomatic/conf_source/ieCe
     [java] Loading configuration resources
     [java] Initialization complete
     [java] Processing started
     [java] Tenant organizations already exists, skipping
     [java] Role ROLE_ADMINISTRATOR already exists, skipping.
     [java] Role ROLE_USER already exists, skipping.
     [java] Role ROLE_ANONYMOUS already exists, skipping.
     [java] User anonymousUser already exists, skipping.
     [java] Created user bobb
     [java] Updated user jasperadmin
     [java] Weak password.

BUILD FAILED
/tmp/jasper-8.0/jasperreports-server-cp-8.0.0-bin/buildomatic/bin/db-common.xml:1465: The following error occurred while executing this line:
/tmp/jasper-8.0/jasperreports-server-cp-8.0.0-bin/buildomatic/bin/import-export.xml:335: The following error occurred while executing this line:
/tmp/jasper-8.0/jasperreports-server-cp-8.0.0-bin/buildomatic/bin/import-export.xml:168: Java returned: 255

 

I found the following article (https://community.jaspersoft.com/wiki/command-line-import-stops-weak-password-error), but I confirmed that we have the expected default setting configured for the "allowedPasswordPattern" in the "applicationContext.xml" file (ie. "^.*$") to not restrict passwords.

I also found the following article (https://community.jaspersoft.com/questions/1157046/jasperserver-upgrade-build-failed-java-returned-255) which contained the "Java returned: 255" error.  However, that one seemed to be an issue with an invalid path to the upgrade zip file.  I do not see the same "java.io.FileNotFoundException" error in my log files.

 

[brodie]

Did you ever get past this?   We are attempting to upgrade from 7.8 to 8.0.   Same thing (different user).

 

[kevin.boerboom]

Hi Brodie - After a bit of investigation we discovered that we were running our Jasper server on an old (and non-supported) version of Postgres database (checked this on https://docs.tibco.com/pub/js-jrs/8.0.0/doc/pdf/TIB_js-jrs_8.0.0_Platform-Support-Commercial-Edition.pdf?id=0).  Ultimately, we never were truly able to pinpoint the root cause, but we assumed it may have been related to the out-of-support version of the Postgres we were using.  We also ran into some issues with performing an "in-place" upgrading of the Postgres database, so we ended up spinning up a new JasperServer altogether (bundled with Postgres).